Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Message-ID: <BLU436-SMTP2488EB2390E6AE5CD4B3CB08FA70@phx.gbl>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: How to make the client fast fail
From: Michael Segel <michael_segel@hotmail.com>
In-Reply-To: 
 <CAGEzYm2tgJ6rgcLxnp+-M8vLm8OaRZaOKa4OLvdxtFmK5+ifaQ@mail.gmail.com>
Date: Tue, 16 Jun 2015 06:59:23 -0700
Content-Transfer-Encoding: quoted-printable
References: 
 <CAGEzYm3pbDbWxY+-D38Q6i_WDGjY2QrWO4+LFZvo4mguRKo+Xg@mail.gmail.com>
 <BLU437-SMTP40B0806406B643231785748FBD0@phx.gbl>
 <CAGEzYm2tgJ6rgcLxnp+-M8vLm8OaRZaOKa4OLvdxtFmK5+ifaQ@mail.gmail.com>
To: user@hbase.apache.org

Be careful for what you wish.=20

You want to fail fast, ok, but when you shorten the HBase timers, you =
can run in to other problems.=20
The simplest solution is to use a timer  / timeout thread in your =
application.=20

You want to do it this way because you are asking for an application =
specific solution while HBase is a shared resource.=20

Failing fast and failing often is no way to run an HBase/Hadoop cluster. =
 ;-)=20

> On Jun 14, 2015, at 10:03 PM, PRANEESH KUMAR =
<praneesh.sankar@gmail.com> wrote:
>=20
> Hi Michael,
>=20
> We can have a monitoring thread and  interrupt the hbase client thread
> after time out instead of doing this I want the timeout or some =
exception
> to be thrown from the HBase client itself.
>=20
> On Thu, Jun 11, 2015 at 5:16 AM, Michael Segel =
<michael_segel@hotmail.com>
> wrote:
>=20
>> threads?
>>=20
>> So that regardless of your hadoop settings, if you want something =
faster,
>> you can use one thread for a timer and then the request is in =
another. So
>> if you hit your timeout before you get a response, you can stop your =
thread.
>> (YMMV depending on side effects=E2=80=A6 )
>>=20
>>> On Jun 10, 2015, at 12:55 AM, PRANEESH KUMAR =
<praneesh.sankar@gmail.com>
>> wrote:
>>>=20
>>> Hi,
>>>=20
>>> I have got the Connection object with default configuration, if the
>>> zookeeper or HMaster or Region server is down, the client didn't =
fast
>> fail
>>> and it took almost 20 mins to thrown an error.
>>>=20
>>> What is the best configuration to make the client fast fail.
>>>=20
>>> Also what is significance of changing the following parameters.
>>>=20
>>> hbase.client.retries.number
>>> zookeeper.recovery.retry
>>> zookeeper.session.timeout
>>> zookeeper.recovery.retry.intervalmill
>>> hbase.rpc.timeout
>>>=20
>>> Regards,
>>> Praneesh
>>=20
>>=20