-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Restrict the priority of ShardSnapshotTask
to the same snapshot only
#89976
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
Restrict the priority of ShardSnapshotTask
to the same snapshot only
#89976
Conversation
Pinging @elastic/es-distributed (Team:Distributed) |
Hi @pxsalehi, I've created a changelog YAML for you. |
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.
LGTM this benchmarks far superior to the previous order of operations. Lets remove the changelog entry and make it a non-issue though since its on top of unreleased work.
CI failure was due to #89776 and unrelated. |
@elasticmachine update branch |
merge conflict between base and head |
…ve-compare-shardSnapshot
…com:pxsalehi/elasticsearch into ps-220909-alternative-compare-shardSnapshot
@elasticmachine run elasticsearch-ci/bwc |
Thanks, Armin! |
Give shard snapshot metadata work priority over file snapshot work ONLY within the same snapshot. After some discussion with Armin and some benchmarks, this seems to prevent many overlapping snapshots prolonging each other due to constant prioritization of snapshot metadata work.