Re: distributing new regions immediately

2017-07-27 Thread jeff saremi
very interesting. Thanks Ted From: Ted Yu <yuzhih...@gmail.com> Sent: Thursday, July 27, 2017 2:13:25 PM To: user@hbase.apache.org Subject: Re: distributing new regions immediately Since you're more concerned with write load, you can take a look at the fol

Re: distributing new regions immediately

2017-07-27 Thread jeff saremi
Thanks Dima From: Dima Spivak <dimaspi...@apache.org> Sent: Thursday, July 27, 2017 12:38:56 PM To: user@hbase.apache.org Subject: Re: distributing new regions immediately Presplitting tables is typically how this is addressed in production cases. On Thu,

Re: distributing new regions immediately

2017-07-27 Thread Ted Yu
Since you're more concerned with write load, you can take a look at the following parameter: hbase.master.balancer.stochastic.writeRequestCost Default value is 5, much smaller than default value for region count cost (500). Consider raising the value so that load balancer reacts more

Re: distributing new regions immediately

2017-07-27 Thread Dima Spivak
Presplitting tables is typically how this is addressed in production cases. On Thu, Jul 27, 2017 at 12:17 PM jeff saremi wrote: > We haven't done enough testing for me to say this with certainty but as we > insert data and new regions get created, it could be a while

distributing new regions immediately

2017-07-27 Thread jeff saremi
We haven't done enough testing for me to say this with certainty but as we insert data and new regions get created, it could be a while before those regions are distributed. As such and if the data injection continues the load on the region server becomes overwhelming Is there a way to