Cluster Health should run on applied states, even if waitFor=0#17440
Merged
bleskes merged 1 commit intoelastic:masterfrom Apr 1, 2016
Merged
Cluster Health should run on applied states, even if waitFor=0#17440bleskes merged 1 commit intoelastic:masterfrom
bleskes merged 1 commit intoelastic:masterfrom
Conversation
Contributor
|
LGTM |
c3e0260 to
24eb0ba
Compare
24eb0ba to
90954ed
Compare
90954ed to
28c468b
Compare
…c#17440 We already protect against making decisions based on an inflight cluster state if someone asks for a waitFor rule (like wait for green). We should do the same for normal health checks as well (unless timeout is set to 0) as it be trappy to debug failures when health says the cluster is in a certain state, but that state wasn't applied yet. Closes elastic#17440
28c468b to
0b12cab
Compare
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
3 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.
We already protect against making decisions based on an inflight cluster state if someone asks for a waitFor rule (like wait for green). We should do the same for normal health checks as well (unless timeout is set to 0) as it be trappy to debug failures when health says the cluster is in a certain state, but that state wasn't applied yet.
Example failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+periodic/270/console