(PC-39002)[API] perf: do not excessively stack ubble celery tasks #20424
Conversation
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
ddb611b to
602a3d1
Compare
ataib-pass
approved these changes
Nov 28, 2025
The previous recovery cron took 170 000 fraud checks and sent them directly to Celery. This causes a lot of tasks to be rate limited and stored in the workers memory, leading to an OOMKill. With the celery feature flag on, the cron will only stack what Celery can realistically do in one hour. The keep the recovery going, the cron should be called every hour.
602a3d1 to
583cbb6
Compare
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.
The previous recovery cron took 170 000 fraud checks and sent them directly to Celery. This causes a lot of tasks to be rate limited and stored in the workers memory, leading to an OOMKill.
With the celery feature flag on, the cron will only stack what Celery can realistically do in one hour. The keep the recovery going, the cron should be called every hour.
🎯 Related Ticket or 🔧 Changes Made
Ticket Jira