Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.160.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1403137117878-4060566.post@n3.nabble.com>
References: <1403112020931-4060560.post@n3.nabble.com>
	<CALte62zXiDNNNe+8MGw_as92_XwDY7g-EqPDQCmmN3mn09divQ@mail.gmail.com>
	<1403137117878-4060566.post@n3.nabble.com>
Date: Wed, 18 Jun 2014 18:07:02 -0700
Message-ID: 
 <CALte62x3hSijmqdCipPDFzc9xMzmbtyxrd5Ek_Gm9VqTNZeXDQ@mail.gmail.com>
Subject: Re: Zookeeper timeout exception seen whenever too much of data is
 being pushed to hbase
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=20cf3010e34d9b3bfc04fc25fe8a

--20cf3010e34d9b3bfc04fc25fe8a
Content-Type: text/plain; charset=UTF-8

I don't have much experience with commons pool framework.

Using HConnection effectively should be the way to go.

Cheers


On Wed, Jun 18, 2014 at 5:18 PM, arunas <sivaram.aruna@gmail.com> wrote:

> Thanks Ted, The link was indeed helpful.
>
> The issue is that whenever we hit this exception, since the HBASE writes
> are
> individual tasks in a threadpool, this exception causes the application to
> go in crazy loop and the handle never comes to the parent thread.
>
> Sesondly, is it a good idea if I write a custom pool which manages the
> htable life cycle using the commons pool framework instead of relying on
> the
> htablepool or the Hconnection??
>
>
>
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/Zookeeper-timeout-exception-seen-whenever-too-much-of-data-is-being-pushed-to-hbase-tp4060560p4060566.html
> Sent from the HBase User mailing list archive at Nabble.com.
>

--20cf3010e34d9b3bfc04fc25fe8a--