Add a client-side time budget to RabbitmqBroker.enqueue - #881
Open
davidt99 wants to merge 1 commit into
Open
Conversation
In a clustered broker, an ungraceful node loss (frozen VM, partition) blocks a confirmed publish for ~net_ticktime (60s) instead of failing fast, and enqueue retries that up to MAX_ENQUEUE_ATTEMPTS times -- a single send can stall for minutes. - dramatiq_max_enqueue_duration: optional per-enqueue wall-clock budget (ms, 0/default off). Checked between attempts, so it caps the retry loop at ~budget + one attempt. - Make MAX_ENQUEUE_ATTEMPTS / MAX_DECLARE_ATTEMPTS env-configurable. - Log exc_info on the retry paths; document the env vars; add a test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
davidt99
force-pushed
the
rabbitmq-enqueue-time-budget
branch
from
July 23, 2026 10:54
c533f38 to
abe0b0c
Compare
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
1 participant
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.
In a clustered broker, an ungraceful node loss (frozen VM, partition) blocks a confirmed publish for ~net_ticktime (60s) instead of failing fast, and enqueue retries that up to MAX_ENQUEUE_ATTEMPTS times -- a single send can stall for minutes.
Although it's more relevant to quorum queues, I've validated it affects also classic queues in a cluster mode.