harden: switch to equal jitter for retry backoff decorrelation#198
harden: switch to equal jitter for retry backoff decorrelation#1980x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
Additive-only jitter produced delays in [raw, raw*1.25] — a 25% spread. In a keeper fleet, all instances retry within the same narrow band after an outage, causing thundering herd. Equal jitter spreads across [raw/2, raw] — 2x the spread with a meaningful minimum backoff floor. Preserves jitterFactor=0 for deterministic test delays. Also applied to discovery.ts withJitter. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 29 minutes and 9 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
[raw, raw*1.25]— only 25% spread[raw/2, raw]— 2x the spread with a meaningful minimum backoff floorjitterFactor: 0still produces deterministic delays for tests (backward compat)discovery.tswithJitterhelper (same additive-only pattern)Test plan
🤖 Generated with Claude Code