Suggested way to simulate client session expiration in unit tests?

2010-07-06 Thread Jeremy Davis
Is there a recommended way of simulating a client session expiration in unit tests? I see a TestableZooKeeper.java, with a pauseCnxn() method that does cause the connection to timeout/disconnect and reconnect. Is there an easy way to push this all the way through to session expiration? Thanks, -JD

Re: Suggested way to simulate client session expiration in unit tests?

2010-07-06 Thread Mahadev Konar
Hi Jeremy, zk.disconnect() is the right way to disconnect from the servers. For session expiration you just have to make sure that the client stays disconnected for more than the session expiration interval. Hope that helps. Thanks mahadev On 7/6/10 9:09 AM, Jeremy Davis

Re: zookeeper crash

2010-07-06 Thread Travis Crawford
Hey all - I believe we just suffered an outage from this issue. Short version is while restarting quorum members with GC flags recommended in the Troubleshooting wiki page a follower logged messages similar two the following jiras: 2010-07-06 23:14:01,438 - FATAL

Re: Suggested way to simulate client session expiration in unit tests?

2010-07-06 Thread Jeremy Davis
Thanks! That seems to work, but it is approximately the same as zooKeeper.close() in that there is no SessionExpired event that comes up through the default Watcher. Maybe I'm assuming more from ZK than I should, but should a paranoid lock implementation periodically test it's session by reading

Re: Suggested way to simulate client session expiration in unit tests?

2010-07-06 Thread Patrick Hunt
If you want to simulate expiration use the example I sent. http://github.com/phunt/zkexamples Another option is to use a mock. Patrick On 07/06/2010 05:42 PM, Jeremy Davis wrote: Thanks! That seems to work, but it is approximately the same as zooKeeper.close() in that there is no