-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix Queued Snapshot Clone not Starting after Data Node Drops Out (#77111
) We have to account for queued up clones when dealing with nodes dropping out and start them when they become ready to execute because of a node leaving the cluster. Added test to reproduce the issue in #77101 and another test to verify that the more complex case of clone queued after snapshot queued after clone still works correctly as well. The solution here is the most direct fix I could think of and the by far easiest to backport. That said, I added a TODO that asks for a follow-up that should allow for completely removing the duplicate code across handling shard updates and external changes. The difference between the two ways of updating the state is a left-over from the time before we had concurrent operations and has become a needless complexity nowadays. closes #77101
- Loading branch information
1 parent
007469a
commit 8b9c52e
Showing
3 changed files
with
163 additions
and
19 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