I agree that more documentation would be better. However,
> Yet, there are some applications which require a faster time out than
> others. So, you tune some of the timers to have a fast fail, and you end up
> causing unintended problems for others.
>
> The simplest solution is to use threads in
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 make this easie
I agree. We have to make this easier - to configure and to understand. And the
default should be better. Looks like they only make sense for long running M/R
jobs.
Lemme check whether there's a jira already; I'll revive it, otherwise I'll
create one and we can have further discussions there.
Tha
Hi,
We are running HBase for a while now with pre-splitted table and we end up
having same number of regions on every node.
But as we add more hardware because of growing size we have very uneven
cluster with different disk size, cpu, memory etc.. this causes problems
related to disk utilization.
Lars,
Sigh.
Yes, configuring your timeouts correctly is important.
Time is very important in distributed systems.
Yet, there are some applications which require a faster time out than others.
So, you tune some of the timers to have a fast fail, and you end up causing
unintended problems f
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.
We are using HBase - 1.0.0. Yes we have went through this blog. But
configuring these parameters, we not able to find out what is the exact
time it takes to fail fast. I am really curious if there could be a single
configuration to ensure client level failing? Also it would be great if
someone can
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-timeouts.html
Using yet more threads to monitor timeouts of another thread is a bad
