Block on kombu producer pool acquire instead of raising LimitExceeded#461
Merged
mvdbeek merged 1 commit intoJun 11, 2026
Merged
Conversation
When many jobs complete simultaneously, all postprocess threads compete for the 10-slot kombu producer pool. The non-blocking acquire() raises LimitExceeded which is not in recoverable_exceptions, crashing the thread and losing the status update. Blocking waits for a free slot instead.
|
Thank you, you are a savior. It was a batch of thousands of small jobs (a hundred of them running in parallel), so it was very possible that a few of them finished at the sme time. |
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
2 participants
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.
When many jobs complete simultaneously, all postprocess threads compete for the 10-slot kombu producer pool. The non-blocking acquire() raises LimitExceeded which is not in recoverable_exceptions, crashing the thread and losing the status update. Blocking waits for a free slot instead.
Reported by @martindemko