Session expiration is due to the server not hearing heartbeats from the client. So either the client is partitioned from the server, or the client is not sending heartbeats for some reason, typically this is due to the client JVM gc'ing or swapping.


On 06/10/2010 04:14 PM, Ted Dunning wrote:
Uh.... the options I was recommending were for your CLIENT.  You should have
similar settings on ZK, but it is your client that is likely to be pausing.

On Thu, Jun 10, 2010 at 4:08 PM, Jordan Zimmerman<

The thing is, this is a test instance (on AWS/EC2) that isn't getting a lot
of traffic. i.e. 1 zookeeper instance that we're testing with.

On Jun 10, 2010, at 4:06 PM, Ted Dunning wrote:


I have seen GC times of>  4 minutes on some large processes.  Better to
the GC parameters so you don't get long pauses.

On it mentions
the "-XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC" options.  I


You may want to tune the actual parameters of the GC itself.  These
not be used in general, but might be helpful for certain kinds of


Finally, you should always add options for lots of GC diagnostics:


On Thu, Jun 10, 2010 at 3:49 PM, Jordan Zimmerman<

If I set my session timeout very high (1 minute) this shouldn't happen,

Reply via email to