hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: HBase for Small Key Value Tables
Date Mon, 29 Aug 2016 17:00:58 GMT
bq. We cannot change the maxregionsize parameter

The region size can be changed on per table basis:

  hbase> alter 't1', MAX_FILESIZE => '134217728'

See the beginning of hbase-shell/src/main/ruby/shell/commands/alter.rb for
more details.


On Sun, Aug 28, 2016 at 10:44 PM, Manish Maheshwari <myloginid@gmail.com>

> Hi,
> We have a scenario where HBase is used like a Key Value Database to map
> Keys to Regions. We have over 5 Million Keys, but the table size is less
> than 7 GB. The read volume is pretty high - About 50x of the put/delete
> volume. This causes hot spotting on the Data Node and the region is not
> split. We cannot change the maxregionsize parameter as that will impact
> other tables too.
> Our idea is to manually inspect the row key ranges and then split the
> region manually and assign them to different region servers. We will
> continue to then monitor the rows in one region to see if needs to be
> split.
> Any experience of doing this on HBase. Is this a recommended approach?
> Thanks,
> Manish

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message