I'm wondering if anyone else saw this. I was running TestReplication
on my machine and I saw it failing in testDeleteTypes trying to
replicate _3_ rows:
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 59.62
sec <<< FAILURE!
Time elapsed: 0.081 sec <<< FAILURE!
java.lang.AssertionError: Waited too much time for put replication
Digging down, I was able to jstack while the test is waiting for
replication and I see:
Thread[REPL IPC Server handler 0 on 62520,5,main]
at java.lang.Object.wait(Native Method)
It stays there the whole time. Adding debug around exists I see:
2012-11-07 10:01:15,759 INFO [REPL IPC Server handler 0 on 62520]
zookeeper.RecoverableZooKeeper(170): Running exists on /2/master
2012-11-07 10:01:20,244 INFO [REPL IPC Server handler 0 on 62520]
zookeeper.RecoverableZooKeeper(184): Done with exists on /2/master
If I turn on debug for ZK I see that ZK doesn't process the exists
until a few ms before the call returns.
FWIW I see other exits() hanging for about 5 seconds in the log, and
it always seems to happen on the first call after the session is
Elliott saw the same issue with his machine yesterday but I'm
wondering if anyone else saw it and/or have a clue.
Jean-Daniel Cryans 2012-11-07, 18:18
Kevin Odell 2012-11-07, 18:22
Jean-Daniel Cryans 2012-11-07, 18:28
Andrew Purtell 2012-11-07, 18:33
Jean-Daniel Cryans 2012-11-07, 18:53