Closed nik9000 closed 7 years ago
The test complains that there is still a cluster state in the pending queue after successful return of ensureGreen. The reason is the following:
callClusterStateListeners(clusterChangedEvent);
task.listener.clusterStateProcessed(task.source, previousClusterState, newClusterState);
This means that there is a small time frame where ensureGreen can complete and call the node stats to find the pending queue still containing the last cluster state update.
I've pushed 86aab98fde
ZenDiscoveryIT#testDiscoveryStats
fails because it sees an unexpected cluster state update during the test. I'm not sure why and don't have time to figure it out right now. Here is the failure link: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=fedora/900/consoleFullThe reproduction line from Jenkins (doesn't reproduce for me though) is:
The interesting logs are:
My theory is that some action from the last test leaked into this test.