Skip to content
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

Conversation

jasontedor
Copy link
Member

@jasontedor jasontedor commented Apr 16, 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.

Closes #29544

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.
@jasontedor jasontedor added >test Issues or PRs that are addressing/adding tests review :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. v7.0.0 v6.3.0 labels Apr 16, 2018
@jasontedor jasontedor requested a review from bleskes April 16, 2018 21:47
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@bleskes
Copy link
Contributor

bleskes commented 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?

@jasontedor jasontedor requested review from bleskes and removed request for bleskes April 17, 2018 12:28
@jasontedor jasontedor merged commit a548a7f into elastic:master Apr 18, 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.
@jasontedor jasontedor deleted the full-cluster-restart-test-recovery-wait branch April 18, 2018 13:17
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/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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants