This is another race. ZkStateReader calls constructState() after it has run notifications, so the test can get a stale view of the cluster state if it calls getClusterState() immediately after it’s been notified. We can add a short delay to the test, but that feels like a bit of a hack - maybe we ought to be collecting up notifications and firing them after the state has been updated?
Alan Woodward www.flax.co.uk > On 3 Jun 2016, at 16:32, Policeman Jenkins Server <jenk...@thetaphi.de> wrote: > > 16188CAA6871F926:69863B2F0113D4AC
