feat(transport): exponential retry backoff for Redis SDK-managed retries#234
Merged
Conversation
Contributor
QualOps Code Quality AnalysisStatus: ✅ PASSED - No issues found Summary
No issues found in the analyzed code. 📊 Full ReportPowered by QualOps |
tsiaeggai
approved these changes
Jun 5, 2026
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.
Add: opt-in exponential backoff between SDK-managed retries on the Redis transport. A failing message is reclaimed once it's been idle for
retry_on_idle_ms × (multiplier ** retry_count), capped atretry_backoff_max_ms, so a repeatedly-failing message backs off (30s → 60s → 120s …) instead of being retried on a fixed clock — giving an overloaded ownstream room to recover.CI: added a Redis service to the test job so the Redis integration suite
(45 tests) actually runs on every PR — it was being silently skipped.