Set the ZK timeout to something like 40ms, and give the GC enough Xmx
so you never risk entering the much dreaded concurrent-mode-failure
whereby the entire heap must be GCed.

Consider testing Java 7 and the G1 GC.

We could get a JNI thread to do this, but no one has done so yet. I am
personally hoping for G1 and in the meantime overprovision our Xmx to
avoid the concurrent mode failures.

-ryan

On Tue, Oct 27, 2009 at 2:59 PM, Zhenyu Zhong <zhongresea...@gmail.com> wrote:
> Ryan,
>
> Thank you very much.
> May I ask whether there are any ways to get around this problem to make
> HBase more stable?
>
> best,
> zhong
>
>
>
> On Tue, Oct 27, 2009 at 4:06 PM, Ryan Rawson <ryano...@gmail.com> wrote:
>
>> There isnt any working code yet. Just an idea, and a prototype.
>>
>> There is some sense that if we can get the G1 GC that we could get rid
>> of all long pauses, and avoid the need for this.
>>
>> -ryan
>>
>> On Mon, Oct 26, 2009 at 2:30 PM, Zhenyu Zhong <zhongresea...@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I am very interesting to the solution that Joey proposed and would like
>> to
>> > have a try.
>> > Does anyone have any ideas on how to deploy this zk_wrapper in JNI
>> > integration?
>> >
>> > I would be very appreciated.
>> >
>> > thanks
>> > zhong
>> >
>>
>

Reply via email to