-
Notifications
You must be signed in to change notification settings - Fork 568
Reschedule control loop after metastore overload rejection #6595
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
Merged
fulmicoton-dd
merged 5 commits into
main
from
codex/reschedule-control-loop-on-overload
Jul 15, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e5df00c
Reschedule control loop after overload rejection
fmassot 4ac3893
Minor change.
fulmicoton-dd 87581ce
fixing flaky test
fulmicoton-dd 350eec2
Fix rustfmt after flaky test update
fmassot e315b95
Merge branch 'main' into codex/reschedule-control-loop-on-overload
fmassot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
When
rebalance_shardsfails intry_open_shardsafterinit_shardssucceeds but beforeopen_shards_on_metastore_and_modelrecords the shard (for example a metastoreTooManyRequests), the initialized shard is neither inserted in the model nor closed. Rescheduling the control loop here makes every subsequent 5s tick allocate and initialize another shard with a new ULID while the metastore remains overloaded, so those unregistered shards/queues accumulate on the ingester until some separate retain-shards sync or restart cleans them up.Useful? React with 👍 / 👎.