Feat/memory#151
Merged
Merged
Conversation
|
@nafiuishaaq Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hardened the background email job processor in email.queue.ts. Jobs now get an explicit Bull timeout plus an in-processor timeout guard, recurring memory sampling logs heap/RSS usage and warns on threshold breaches, and shutdown now clears monitors, detaches queue listeners, and closes queues cleanly so listeners and timers do not accumulate.
I also added per-job cleanup in the processor finally path to drop large job payload references after execution, and a periodic queue-history cleanup pass so completed/failed job retention stays bounded. Coverage for the new behavior is in email.queue.spec.ts, including timeout enforcement and shutdown cleanup.
Closes #105