-
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
[CI] MockDiskUsagesIT.testAutomaticReleaseOfIndexBlock fails #45338
Labels
:Distributed Coordination/Allocation
All issues relating to the decision making around placing a shard (both master logic & on the nodes)
>test-failure
Triaged test failures from CI
Comments
dimitris-athanasiou
added
>test-failure
Triaged test failures from CI
:Distributed Coordination/Allocation
All issues relating to the decision making around placing a shard (both master logic & on the nodes)
labels
Aug 8, 2019
Pinging @elastic/es-distributed |
This test was introduced recently in #42559 |
dimitris-athanasiou
added a commit
that referenced
this issue
Aug 8, 2019
dimitris-athanasiou
added a commit
that referenced
this issue
Aug 8, 2019
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Aug 8, 2019
Today the test waits for one of the shards to be blocked, but this does not mean that the block has been applied on all nodes, so a subsequent indexing operation may still go through. Fixes elastic#45338
original-brownbear
pushed a commit
to original-brownbear/elasticsearch
that referenced
this issue
Aug 8, 2019
Today the test waits for one of the shards to be blocked, but this does not mean that the block has been applied on all nodes, so a subsequent indexing operation may still go through. Fixes elastic#45338
original-brownbear
pushed a commit
that referenced
this issue
Aug 8, 2019
Today the test waits for one of the shards to be blocked, but this does not mean that the block has been applied on all nodes, so a subsequent indexing operation may still go through. Fixes #45338
original-brownbear
added a commit
that referenced
this issue
Aug 8, 2019
This failed again today:
Reproduction line (this did not reproduce for me) is:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=java12,nodes=general-purpose/240/console |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Oct 1, 2019
Today the comment boldly claims that this line of code keeps nodes above the 10-byte low watermark when in fact this is not true at all. This change fixes this so that it really does keep nodes above the low watermark. Fixes elastic#45338. Again.
DaveCTurner
added a commit
that referenced
this issue
Oct 1, 2019
Today the comment boldly claims that this line of code keeps nodes above the 10-byte low watermark when in fact this is not true at all. This change fixes this so that it really does keep nodes above the low watermark. Fixes #45338. Again.
DaveCTurner
added a commit
that referenced
this issue
Oct 1, 2019
Today the comment boldly claims that this line of code keeps nodes above the 10-byte low watermark when in fact this is not true at all. This change fixes this so that it really does keep nodes above the low watermark. Fixes #45338. Again.
DaveCTurner
added a commit
that referenced
this issue
Oct 1, 2019
Today the comment boldly claims that this line of code keeps nodes above the 10-byte low watermark when in fact this is not true at all. This change fixes this so that it really does keep nodes above the low watermark. Fixes #45338. Again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Allocation
All issues relating to the decision making around placing a shard (both master logic & on the nodes)
>test-failure
Triaged test failures from CI
Build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+release-tests/232/console
Build scan: https://gradle.com/s/wnz3akbwhhnne
Reproduce with:
Failure:
Could not reproduce locally.
The text was updated successfully, but these errors were encountered: