On Jun 9, 2010, at 4:21 PM, Patrick Hunt wrote:
> In particular you might look at GC/swapping on your clients, that's the most
> common case we see for session expiration (apart from the obvious -- network
> level connectivity failures). In one case I remember there was very heavy
> network lo
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 wrote:
> The thing is, this is a test instance (on AWS/EC2) that isn't getting a lot
> of tra
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:
> Possibly.
>
> I have seen GC times of > 4 minutes on some large processes. Better to set
> the GC paramet
Possibly.
I have seen GC times of > 4 minutes on some large processes. Better to set
the GC parameters so you don't get long pauses.
On http://wiki.apache.org/hadoop/ZooKeeper/Troubleshooting it mentions using
the "-XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC" options. I recommend
adding
