-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix full cluster restart test recovery #29545
Merged
jasontedor
merged 4 commits into
elastic:master
from
jasontedor:full-cluster-restart-test-recovery-wait
Apr 18, 2018
Merged
Fix full cluster restart test recovery #29545
jasontedor
merged 4 commits into
elastic:master
from
jasontedor:full-cluster-restart-test-recovery-wait
Apr 18, 2018
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
The test was using a parameter on GET /_cluster/health that older nodes do not understand. To circumvent this, we check the version of the node if the node does not support the parameter we use the cat shards API to check that all shards for the test index are started.
Pinging @elastic/es-distributed |
nik9000
approved these changes
Apr 17, 2018
Thanks @jasontedor for picking this up. I was wondering this morning - since we know we have a two nodes cluster - can't we use ensureGreen and be happy? |
bleskes
approved these changes
Apr 17, 2018
jasontedor
added a commit
that referenced
this pull request
Apr 18, 2018
The test was using a parameter on GET /_cluster/health that older nodes do not understand. Yet, we do no even need to make this call here, we can use ensure green for the index.
dnhatn
added a commit
that referenced
this pull request
Apr 18, 2018
* master: Remove the index thread pool (#29556) Remove extra copy in ScriptDocValues.Strings Fix full cluster restart test recovery (#29545) Fix binary doc values fetching in _search (#29567) Mutes failing MovAvgIT tests Fix the assertion message for an incorrect current version. (#29572) Fix the version ID for v5.6.10. (#29570) Painless Spec Documentation Clean Up (#29441) Add versions 5.6.10 and 6.2.5 [TEST] test against scaled value instead of fixed epsilon in MovAvgIT Remove `flatSettings` support from request classes (#29560) MapperService to wrap a single DocumentMapper. (#29511) Fix dependency checks on libs when generating Eclipse configuration. (#29550) Add null_value support to geo_point type (#29451) Add documentation about the include_type_name option. (#29555) Enforce translog access via engine (#29542)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/Recovery
Anything around constructing a new shard, either from a local or a remote source.
>test
Issues or PRs that are addressing/adding tests
v6.3.0
v7.0.0-beta1
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.
The test was using a parameter on GET /_cluster/health that older nodes do not understand. Yet, we do no even need to make this call here, we can use ensure green for the index.
Closes #29544