Increased timeout in ClusterServiceTests.testTimeoutUpdateTask to 100ms
The previous 2ms timeout was too small and caused a racing condition in timeout handling. This will be fixed but requires more work.
This commit is contained in:
parent
a668cd22d8
commit
33e49a55f7
|
@ -83,7 +83,7 @@ public class ClusterServiceTests extends ElasticsearchIntegrationTest {
|
||||||
clusterService1.submitStateUpdateTask("test2", new TimeoutClusterStateUpdateTask() {
|
clusterService1.submitStateUpdateTask("test2", new TimeoutClusterStateUpdateTask() {
|
||||||
@Override
|
@Override
|
||||||
public TimeValue timeout() {
|
public TimeValue timeout() {
|
||||||
return TimeValue.timeValueMillis(2);
|
return TimeValue.timeValueMillis(100);
|
||||||
}
|
}
|
||||||
|
|
||||||
@Override
|
@Override
|
||||||
|
@ -102,7 +102,7 @@ public class ClusterServiceTests extends ElasticsearchIntegrationTest {
|
||||||
}
|
}
|
||||||
});
|
});
|
||||||
|
|
||||||
assertThat(timedOut.await(500, TimeUnit.MILLISECONDS), equalTo(true));
|
assertThat(timedOut.await(1000, TimeUnit.MILLISECONDS), equalTo(true));
|
||||||
block.countDown();
|
block.countDown();
|
||||||
Thread.sleep(100); // sleep a bit to double check that execute on the timed out update task is not called...
|
Thread.sleep(100); // sleep a bit to double check that execute on the timed out update task is not called...
|
||||||
assertThat(executeCalled.get(), equalTo(false));
|
assertThat(executeCalled.get(), equalTo(false));
|
||||||
|
|
Loading…
Reference in New Issue