response.
So we scored out the timer option.
Thanks,
Hari
-Original Message-
From: Michael Segel [mailto:michael_se...@hotmail.com]
Sent: Thursday, June 11, 2015 5:17 AM
To: user@hbase.apache.org
Subject: Re: How to make the client fast fail
threads?
So that regardless of your hadoop
quences if an application suddenly
> >> starts to drop connections before a result or timeout occurs too. ;-)
> >>
> >>
> >>> On Jun 16, 2015, at 12:13 AM, lars hofhansl wrote:
> >>>
> >>> Please always tell us which version of HBase you ar
lars hofhansl wrote:
>>>
>>> Please always tell us which version of HBase you are using. We have
>> fixed a lot of issues in this area over time.Here's an _old_ blog post I
>> wrote about this:
>> http://hadoop-hbase.blogspot.com/2012/09/hbase-client-timeou
I
> wrote about this:
> http://hadoop-hbase.blogspot.com/2012/09/hbase-client-timeouts.html
> >
> > Using yet more threads to monitor timeouts of another thread is a bad
> idea, especially when the timeout is configurable in the first place.
> >
> > -- Lars
> >
Filed https://issues.apache.org/jira/browse/HBASE-13919, please chime in there.
Thanks.
-- LarsÂ
From: lars hofhansl
To: mukund murrali ; "user@hbase.apache.org"
Sent: Tuesday, June 16, 2015 12:37 PM
Subject: Re: How to make the client fast fail
I agree. We have to
scussions there.
Thanks for pointing this issue out.
-- Lars
From: mukund murrali
To: user@hbase.apache.org; lars hofhansl
Sent: Tuesday, June 16, 2015 12:21 AM
Subject: Re: How to make the client fast fail
We are using HBase - 1.0.0. Yes we have went through this blog. But con
imeout is configurable in the first place.
>
> -- Lars
> From: mukund murrali
> To: user@hbase.apache.org
> Sent: Sunday, June 14, 2015 10:22 PM
> Subject: Re: How to make the client fast fail
>
> It would be great if there is a single timeout configuration from th
Be careful for what you wish.
You want to fail fast, ok, but when you shorten the HBase timers, you can run
in to other problems.
The simplest solution is to use a timer / timeout thread in your application.
You want to do it this way because you are asking for an application specific
solut
In addition to 1.0.0, also suggest for 0.94.15.
Thanks,
Hari
-Original Message-
From: mukund murrali [mailto:mukundmurra...@gmail.com]
Sent: Tuesday, June 16, 2015 12:52 PM
To: user@hbase.apache.org; lars hofhansl
Subject: Re: How to make the client fast fail
We are using HBase - 1.0.0
gt; Sent: Sunday, June 14, 2015 10:22 PM
> Subject: Re: How to make the client fast fail
>
> It would be great if there is a single timeout configuration from the
> client end. All other parameters should fine tune based on that one
> parameter. We have modified simple based on
is a bad idea,
especially when the timeout is configurable in the first place.
-- Lars
From: mukund murrali
To: user@hbase.apache.org
Sent: Sunday, June 14, 2015 10:22 PM
Subject: Re: How to make the client fast fail
It would be great if there is a single timeout configuration fro
inal Message-
> From: PRANEESH KUMAR [mailto:praneesh.san...@gmail.com]
> Sent: Monday, June 15, 2015 10:33 AM
> To: user@hbase.apache.org
> Subject: Re: How to make the client fast fail
>
> Hi Michael,
>
> We can have a monitoring thread and interrupt the hbase client thre
...@gmail.com]
Sent: Monday, June 15, 2015 10:33 AM
To: user@hbase.apache.org
Subject: Re: How to make the client fast fail
Hi Michael,
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
Hi Michael,
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.
On Thu, Jun 11, 2015 at 5:16 AM, Michael Segel
wrote:
> threads?
>
> So that regardless of your
threads?
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… )
> On Jun 10, 2015, at 1
Hi,
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.
What is the best configuration to make the client fast fail.
Also what is significance of changing the
16 matches
Mail list logo
