fix: increase scheduler error tolerance for transient Redis outages#881
Merged
Conversation
The logmq consumer was incorrectly using DeliveryMaxConcurrency instead of LogMaxConcurrency, causing LOG_MAX_CONCURRENCY to be ignored and Pub/Sub to cap unacked messages at the delivery limit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… outages Previously the scheduler gave up after 5 consecutive errors (~3s), permanently killing the retrymq worker with no recovery path. A brief Dragonfly Cloud restart would take down retries across all outpost-cloud deployments until containers were manually restarted. Increase to 15 errors with 60s backoff cap (~7 min tolerance window). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alexluong
force-pushed
the
fix/scheduler-retry-resilience
branch
from
ee47766 to
e847146
Compare
mkherlakian
approved these changes
Apr 25, 2026
2 tasks
alexluong
added a commit
that referenced
this pull request
May 13, 2026
) Previously the consumer gave up after 5 consecutive receive errors with a 5s backoff cap (~3s total tolerance), permanently killing the worker with no recovery path. A brief broker hiccup (e.g. GCP OAuth/DNS blip, managed broker restart) was enough to take down logmq/deliverymq workers across deployments until containers were manually restarted. Mirrors the same fix applied to the retrymq scheduler in #881. Increase to 10 errors with 15s backoff cap (~1 min tolerance window). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
maxConsecutiveErrorsfrom 5 → 10 andmaxErrorBackofffrom 5s → 15sReceiveMessageis sufficient to recover from transient outagesTest plan
scheduler_test.gopasses🤖 Generated with Claude Code