Fix ClusterDisruptionIT.testAckedIndexing (#53169)
Use assertBusy when doing reroute after bridged disruption, since it can return non-acked if a node is marked faulty by follower check after disruption ended. Closes #53064
This commit is contained in:
parent
6a5d9195aa
commit
2e924e4a83
|
@ -227,7 +227,7 @@ public class ClusterDisruptionIT extends AbstractDisruptionTestCase {
|
|||
// is the super-connected node and recovery source and target are on opposite sides of the bridge
|
||||
if (disruptionScheme instanceof NetworkDisruption &&
|
||||
((NetworkDisruption) disruptionScheme).getDisruptedLinks() instanceof Bridge) {
|
||||
assertAcked(client().admin().cluster().prepareReroute().setRetryFailed(true));
|
||||
assertBusy(() -> assertAcked(client().admin().cluster().prepareReroute().setRetryFailed(true)));
|
||||
}
|
||||
ensureGreen("test");
|
||||
|
||||
|
|
Loading…
Reference in New Issue