See Section 2.5.2, “Recommended Configurations”.
The number of regions for an HBase table is driven by the Section 2.5.2.6, “Bigger Regions”. Also, see the architecture section on Section 9.7.1, “Region Size”
For larger systems, managing compactions and splits may be something you want to consider.
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.
Have HBase write the checksum into the datablock and save having to do the checksum seek whenever you read.
See hbase.regionserver.checksum.verify
,
hbase.hstore.bytes.per.checksum
and hbase.hstore.checksum.algorithm
For more information see the
release note on HBASE-5074 support checksums in HBase block cache.