That's very interesting results, a good job sleuthing. You might try the
concurrent collector?
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html#available_collectors.selecting
specifically item 4 -XX:+UseConcMarkSweepGC
I've never used this before myself but it's supposed to
]
Sent: Thursday, February 26, 2009 1:31 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: Recommended session timeout
I've answered the questions you asked previously below, but I thought
I would open with the actual culprit now that we found it. When I said
loading data before, what I was talking
away after session timeout.
I have seen some users using 10-15 seconds of session timeout, but you
should use as per your application requirements.
Hope this helps.
mahadev
On 2/22/09 3:09 AM, Joey Echeverria joe...@gmail.com wrote:
Is there a recommended session timeout? Does it change based
should use as per your application requirements.
Hope this helps.
mahadev
On 2/22/09 3:09 AM, Joey Echeverria joe...@gmail.com wrote:
Is there a recommended session timeout? Does it change based on the
ensemble size?
Thanks,
-Joey
, but you
should use as per your application requirements.
Hope this helps.
mahadev
On 2/22/09 3:09 AM, Joey Echeverria joe...@gmail.com wrote:
Is there a recommended session timeout? Does it change based on the
ensemble size?
Thanks,
-Joey
Is there a recommended session timeout? Does it change based on the
ensemble size?
Thanks,
-Joey
