Re: distributing new regions immediately

very interesting. Thanks Ted From: Ted Yu 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 following

Re: distributing new regions immediately

Thanks Dima From: Dima Spivak 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, Jul

Graph Analytics on HBase With HGraphDB and Apache Flink Gelly

For those who are interested, yet another blog on analyzing graphs stored in HBase, this time with Apache Flink Gelly: https://yokota.blog/2017/07/27/graph-analytics-on-hbase-with-hgraphdb-and-apache-flink-gelly/

Re: distributing new regions immediately

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

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

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

Re: HBase GET operation max row size - partial results

AFAIK there's no max result size or partial result for get request. If we add such feature in future, we will add release note in JIRA. (Actually we have implemented such limit in our customized version and it requires CP to correctly handle it, we may upstream the feature later) Some more