TEST: Attempt to issue synced-flush from allocated nodes #29680
Closed
Conversation
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
Today, SyncedFlushUtil attempts to issue synced-flush from any node in the cluster. Rarely, the synced-flush was issued from a node which has not received the latest routing table information. The (incomplete) debug log shows that the synced-flush result does not include any active shard. This change makes sure that we only issue synced-flush nodes which are assigned shards from the requesting index. Closes elastic#29392
|
@bleskes Can you please take a look? I am unable to make a review request. Thank you! |
dnhatn
added
the
:Distributed Indexing/Recovery
|
Pinging @elastic/es-distributed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Today, SyncedFlushUtil attempts to issue synced-flush from any node in
the cluster. Rarely, the synced-flush was issued from a node which has
not received the latest routing table information. The (incomplete)
debug log shows that the synced-flush result does not include any active
shard.
This change makes sure that we only issue synced-flush nodes which are
assigned shards from the requesting index.
Closes #29392