See Section 2.8.2, “Recommended Configuations”.
The number of regions for an HBase table is driven by the Section 2.8.2.6, “Bigger Regions”. Also, see the architecture section on Section 8.6.1, “Region Size”
A lower number of regions is preferred, generally in the range of 20 to low-hundreds per RegionServer. Adjust the regionsize as appropriate to achieve this number.
For the 0.90.x codebase, the upper-bound of regionsize is about 4Gb. For 0.92.x codebase, due to the HFile v2 change much larger regionsizes can be supported (e.g., 20Gb).
You may need to experiment with this setting based on your hardware configuration and application needs.
For larger systems, managing compactions and splits may be something you want to consider.
See hbase.regionserver.handler.count
.
This setting in essence sets how many requests are
concurrently being processed inside the RegionServer at any
one time. If set too high, then throughput may suffer as
the concurrent requests contend; if set too low, requests will
be stuck waiting to get into the machine. You can get a
sense of whether you have too little or too many handlers by
Section 11.2.2.1, “Enabling RPC-level logging”
on an individual RegionServer then tailing its logs (Queued requests
consume memory).
See hfile.block.cache.size
.
A memory setting for the RegionServer process.
See hbase.regionserver.global.memstore.upperLimit
.
This memory setting is often adjusted for the RegionServer process depending on needs.
See hbase.regionserver.global.memstore.lowerLimit
.
This memory setting is often adjusted for the RegionServer process depending on needs.
See hbase.hstore.blockingStoreFiles
.
If there is blocking in the RegionServer logs, increasing this can help.
See hbase.hregion.memstore.block.multiplier
.
If there is enough RAM, increasing this can help.