Re: Right value for hbase.rpc.timeout

(i.e. how many of these 75G regions you have)? Thanks. -- Lars From: Dejan Menges dejan.men...@gmail.com To: user@hbase.apache.org user@hbase.apache.org Sent: Monday, May 4, 2015 1:31 AM Subject: Re: Right value for hbase.rpc.timeout Hi Ted, Max filesize for region is set to 75G

Re: Right value for hbase.rpc.timeout

have overall (i.e. how many of these 75G regions you have)? Thanks. -- Lars From: Dejan Menges dejan.men...@gmail.com To: user@hbase.apache.org user@hbase.apache.org Sent: Monday, May 4, 2015 1:31 AM Subject: Re: Right value for hbase.rpc.timeout Hi Ted, Max filesize

Re: Right value for hbase.rpc.timeout

Hi Ted, Max filesize for region is set to 75G in our case. Regarding split policy we use most likely ConstantSizeRegionSplitPolicy http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/ConstantSizeRegionSplitPolicy.html (it's 0.98.0 with bunch of patches and that should be default

Re: Right value for hbase.rpc.timeout

Sorry, maybe I'm wrong: I made my conclusion based on what I read http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/ that's default; now just found in HBase Book that: hbase.regionserver.region.split.policy Description A split policy determines when a region should be split.

Re: Right value for hbase.rpc.timeout

Please see https://issues.apache.org/jira/browse/HBASE-10501 and https://issues.apache.org/jira/browse/HBASE-10716 Cheers On Mon, May 4, 2015 at 1:43 AM, Dejan Menges dejan.men...@gmail.com wrote: Sorry, maybe I'm wrong: I made my conclusion based on what I read

Re: Right value for hbase.rpc.timeout

Cool, thanks a lot! :) On Mon, May 4, 2015 at 4:14 PM Ted Yu yuzhih...@gmail.com wrote: Please see https://issues.apache.org/jira/browse/HBASE-10501 and https://issues.apache.org/jira/browse/HBASE-10716 Cheers On Mon, May 4, 2015 at 1:43 AM, Dejan Menges dejan.men...@gmail.com wrote:

Re: Right value for hbase.rpc.timeout

Hm, one thing we did - going back through thread - we decided to manually set hbase.master.loadbalance.bytable to true, no matter that by documentation it's true by default. And on our 0.98.0 (2.1.10 by Hortonworks) it finally really balanced regions evenly by tables we had :/ On Mon, May 4, 2015

Re: Right value for hbase.rpc.timeout

Subject: Re: Right value for hbase.rpc.timeout Hi Ted, Max filesize for region is set to 75G in our case. Regarding split policy we use most likely ConstantSizeRegionSplitPolicy http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/ConstantSizeRegionSplitPolicy.html (it's

Right value for hbase.rpc.timeout

Hi, What's the best practice to calculate this value for your cluster, if there is some? In some situations we saw that some maps are taking more than default 60 seconds which was failing specific map job (as if it failed once, it failed also every other time by number of configured retries). I

Re: Right value for hbase.rpc.timeout

Please take a look at 98.3 under http://hbase.apache.org/book.html#trouble.client BTW what's the value for hbase.hregion.max.filesize ? Which split policy do you use ? Cheers On Thu, Apr 30, 2015 at 6:59 AM, Dejan Menges dejan.men...@gmail.com wrote: Basically how I came to this question -

Re: Right value for hbase.rpc.timeout

There is no single ‘right’ value. As you pointed out… some of your Mapper.map() iterations are taking longer than 60 seconds. The first thing is to determine why that happens. (It could be normal, or it could be bad code on your developers part. We don’t know.) The other thing is that if