Fix primary relocation for shadow replicas #22474
Merged
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.
Primary relocation for shadow replicas is broken as the recovery process accesses the engine on the source shard after it's been closed. This results in the source shard failing itself. This has not been detected by tests as, after failing source and target shard of the relocation, the master simply reassigns the primary to the node where it wanted to relocate to as every node has access to the shard files.
Test failure exhibiting behavior (might be an un-related issue though):
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+periodic/1282/consoleFull
Relates to #20300