-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] Various tests in ShrinkIndexIT fail with "expected at least one master-eligible node left" #44164
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
Labels
:Distributed Indexing/Distributed
A catch all label for anything in the Distributed Indexing Area. Please avoid if you can.
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-distributed |
droberts195
added a commit
that referenced
this issue
Jul 10, 2019
droberts195
added a commit
that referenced
this issue
Jul 10, 2019
I can easily reproduce this on |
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 11, 2019
* Move this test suit to cluster scope. Currently, `testShrinkThenSplitWithFailedNode` stops a random node which randomly turns out to be the only shared master node so the cluster reset fails on account of the fact that no shared master node survived. * Closes elastic#44164
Merged
pull bot
pushed a commit
to Pandinosaurus/elasticsearch
that referenced
this issue
Jul 11, 2019
* Fix ShrinkIndexIT * Move this test suit to cluster scope. Currently, `testShrinkThenSplitWithFailedNode` stops a random node which randomly turns out to be the only shared master node so the cluster reset fails on account of the fact that no shared master node survived. * Closes elastic#44164
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 11, 2019
* Fix ShrinkIndexIT * Move this test suit to cluster scope. Currently, `testShrinkThenSplitWithFailedNode` stops a random node which randomly turns out to be the only shared master node so the cluster reset fails on account of the fact that no shared master node survived. * Closes elastic#44164
original-brownbear
added a commit
that referenced
this issue
Jul 11, 2019
* Fix ShrinkIndexIT * Move this test suit to cluster scope. Currently, `testShrinkThenSplitWithFailedNode` stops a random node which randomly turns out to be the only shared master node so the cluster reset fails on account of the fact that no shared master node survived. * Closes #44164
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Indexing/Distributed
A catch all label for anything in the Distributed Indexing Area. Please avoid if you can.
>test-failure
Triaged test failures from CI
Uh oh!
There was an error while loading. Please reload this page.
This failure has occurred many times in the last 36 hours: https://build-stats.elastic.co/app/kibana#/discover?_g=(refreshInterval:(pause:!t,value:0),time:(from:now-30d,mode:relative,to:now))&_a=(columns:!(test,build-id,build_url,branch),filters:!(),index:e58bf320-7efd-11e8-bf69-63c8ef516157,interval:auto,query:(language:lucene,query:'class:%20%22org.elasticsearch.action.admin.indices.create.ShrinkIndexIT%22'),sort:!(time,desc))
Often the failing test is
ShrinkIndexIT.testCreateShrinkWithIndexSort
, see for example https://gradle.com/s/fglguuelmqobeMore recently a failure of
ShrinkIndexIT.testShrinkCommitsMergeOnIdle
was seen but with the same error message: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-1/2405/testReport/junit/org.elasticsearch.action.admin.indices.create/ShrinkIndexIT/testShrinkCommitsMergeOnIdle/In both cases the error message is something like:
A REPRO command for 7.x is:
A REPRO command for master is:
Neither of these reproduce locally for me.
I will mute the suite.
The text was updated successfully, but these errors were encountered: