On Tue, Jan 3, 2012 at 4:26 PM, Jordan Zimmerman <[email protected]> wrote: > These are highly contrived scenarios. They all involve unit tests and the > jerry-rigged TestingServer that I use for Curator > (https://github.com/Netflix/curator/blob/master/curator-test/src/main/java/ > com/netflix/curator/test/TestingServer.java). > >>How much longer? > It turns out that I had a number of tests that (incorrectly) were not > waiting for SysConnected. I had to add in a wait (Curator's > blockUntilConnectedOrTimedOut()). So, the implication is that when using > ZK 3.3.x SysConnected for my unit tests was nearly instantaneous and now > it takes more than a few milliseconds.
We've seen this in our tests prior to 3.4. We'll have tests that run fine for a long time, then occasionally fail. When we looked we found the test had a flaw similar to what you describe. It's a timing issue for sure, but something the test needs to handle. Patrick
