This repository was archived by the owner on Dec 1, 2025. It is now read-only.
Reproduce incident 8197 stuck processing #225
Draft
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.
Context
Don't merge, just a temporal test to reproduce the issue we had with rate limits.
We had a rate limited task set to 0.5/min. The message processing lag started to increase and the rate limited task was not running. You can find more details in the incident thread.
When we removed the rate limiter, that task started to run.
I added a test to try to reproduce this issue: taskWithRateLimitingConcurrencyPolicyWillNotHangWithManyTasks
It looks like the problem is related to the number of registered tasks.
With allTasks = 10000;
Checklist