-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix stuck backfill when scheduled work queue is at capacity #5575
Conversation
2964f1c
to
20d0110
Compare
20d0110
to
4f8c6ac
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This style of test seems like a good way to deal with timings! Nice!
|
||
// Advance the time by more than 1/2 the slot to trigger a scheduled backfill batch to be sent. | ||
// This should fail as the `ready_work` channel is at capacity, and it should be rescheduled. | ||
let more_than_half_slot = Duration::from_secs(slot_duration / 2 + 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is to hit the timing defined by BACKFILL_SCHEDULE_IN_SLOT
, right? Can we use that directly here so as to not break this test in the future if this schedule changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in a5f76ce
…x-stuck-backfill
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 532206e |
Issue Addressed
Addresses #5504.
Fix stuck backfill when scheduled work queue is at capacity and make sure the batch is rescheduled.
Additional Info
I tried adding a regression test but can't get it to pass. Will look into it next week.(fixed)