Replace SCAN-based outbox delete with reverse index in Redis store#186
Replace SCAN-based outbox delete with reverse index in Redis store#186andrewwormald merged 2 commits intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|



Problem
DeleteOutboxEventusesSCANto iterate all outbox keys, then runs a Lua script doingLRANGE 0 -1on each. This is O(workflows * events) — it won't scale.Why
The code itself had a TODO acknowledging this. As workflows and events grow, delete latency grows linearly and blocks the outbox consumer.
Fix
Add a reverse index (
outbox-event-id -> outbox-key) written atomically in the store Lua script.DeleteOutboxEventnow does a singleGET+ targetedLREM.🤖 Generated with Claude Code