Repository navigation
docs: administration: scheduling-and-retries: document retry deferral under flush limit - #2764
Conversation
… under flush limit
- Document that a retry is rescheduled without counting against
Retry_Limit when too many flush requests are in flight
Signed-off-by: Eric D. Schabell <eric@schabell.org>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughThe scheduling and retries guide adds a note that Fluent Bit v5.1.3 or later reschedules a retry without counting it against ChangesRetry scheduling documentation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to The documentation accurately describes retry deferral starting in v5.1.3; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@patrick-stephens ready for review! |
Retry_Limit when too many flush requests are in flight
Signed-off-by: Eric D. Schabell eric@schabell.org
Summary by CodeRabbit
Retry_Limitwhen too many flush requests are in flight.