forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove Redundant CS Update during Snapshot Delete
Same as elastic#55276 but for snapshot deletes. This change folds the removal of the snapshot delete state entry into the the safe generation step where possible. This measn that for repositories that write shard generations, the time the snapshot delte entry will stay in the cluster state will be shortened a lot and reduced to the time it takes to update the repository metadata. It is fully safe in this case to run other snapshot operations after the metadata. We can not do this for repositories that do not write shard generations so those need to go through a different path and submit a separate state update task still. Also, this PR fixes a problem with the cooldown period for S3 non-shard-generation repos introduced by elastic#55286. We can not run the state update outright in the repository because we enforce the cooldown via the listener wrapping. I fixed this by folding the final state update into the listener in this case.
- Loading branch information
1 parent
30d8e1f
commit 960f861
Showing
8 changed files
with
88 additions
and
44 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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