-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Reduce assertBusy
usage in testMultipleNodes
#126582
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
Reduce assertBusy
usage in testMultipleNodes
#126582
Conversation
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks for fixing it up.
@@ -124,10 +124,6 @@ protected void deleteMonitoringIndices() { | |||
assertAcked(client().admin().indices().prepareDelete(ALL_MONITORING_INDICES)); | |||
} | |||
|
|||
protected void ensureMonitoringIndicesYellow() { | |||
ensureYellowAndNoInitializingShards(".monitoring-es-*"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ALL_MONITORING_INDICES
is "monitoring-*
and this is .monitoring-es-*
. I doubt the difference would actual matter. But probably still better to be safe and use .monitoring-es-*
in awaitClusterState?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah well spotted :) Yeah it doesn't matter I think, we're only monitoring ES itself in this test, but I fixed that up.
Relates #126501