Ensure relocation occur in testRelocationWithConcurrentIndexing#40801
Merged
dnhatn merged 4 commits intoelastic:masterfrom Apr 7, 2019
Merged
Ensure relocation occur in testRelocationWithConcurrentIndexing#40801dnhatn merged 4 commits intoelastic:masterfrom
dnhatn merged 4 commits intoelastic:masterfrom
Conversation
dnhatn
added
>test
Collaborator
|
Pinging @elastic/es-distributed |
henningandersen
approved these changes
Apr 4, 2019
Contributor
henningandersen
left a comment
henningandersen
left a comment
There was a problem hiding this comment.
LGTM.
Thanks @dnhatn , I left one optional comment to consider.
qa/rolling-upgrade/src/test/java/org/elasticsearch/upgrades/RecoveryIT.java
Outdated
Show resolved
Hide resolved
Member
Author
|
Thanks @henningandersen |
dnhatn
added a commit
that referenced
this pull request
Apr 9, 2019
If the relocation is throttled, the subsequent search request on the target node (i.e., with preference _only_nodes=target_node) will fail because some shards have not moved to that node yet. With this change, we will wait for the relocation happens by busily checking the routing table of the testing index on the target node. Closes #34950
dnhatn
added a commit
that referenced
this pull request
Apr 11, 2019
If the relocation is throttled, the subsequent search request on the target node (i.e., with preference _only_nodes=target_node) will fail because some shards have not moved to that node yet. With this change, we will wait for the relocation happens by busily checking the routing table of the testing index on the target node. Closes #34950
dnhatn
added a commit
that referenced
this pull request
Apr 11, 2019
If the relocation is throttled, the subsequent search request on the target node (i.e., with preference _only_nodes=target_node) will fail because some shards have not moved to that node yet. With this change, we will wait for the relocation happens by busily checking the routing table of the testing index on the target node. Closes #34950
gurkankaymak
pushed a commit
to gurkankaymak/elasticsearch
that referenced
this pull request
May 27, 2019
…tic#40801) If the relocation is throttled, the subsequent search request on the target node (i.e., with preference _only_nodes=target_node) will fail because some shards have not moved to that node yet. With this change, we will wait for the relocation happens by busily checking the routing table of the testing index on the target node. Closes elastic#34950
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
If the relocation is throttled, the subsequent search request on the target node (i.e., with preference
_only_nodes=target_node) will fail because some shards have not moved to that node yet. With this change, we will wait for the relocation happens by busily checking the routing table of the testing index on the target node.Closes #34950