Hi all,
The default size of Hbase.hregion.memstore.flush.size is define as 128 MB for
Hbase.hregion.memstore.flush.size. Could anyone kindly explain what would be
the impact if we increase this to a higher value 512 MB or 800 MB or higher.
We have a very write heavy cluster. Also we run
Related please see HBASE-13408 HBase In-Memory Memstore Compaction
FYI
On Mon, Aug 24, 2015 at 10:32 AM, Jean-Marc Spaggiari
jean-m...@spaggiari.org wrote:
The split policy also uses the flush size to estimate how to split
tables...
It's sometime fine to upgrade thise number a bit. Like,
1. How many regions per RS?
2. What is your dfs.block.size?
3. What is your hbase.regionserver.maxlogs?
Flush can be requested when:
1. Region size exceeds hbase.hregion.memstore.flush.size
2. Region's memstore is too old (periodic memstore flusher checks the age
of memstore, default is 1hour)
The split policy also uses the flush size to estimate how to split tables...
It's sometime fine to upgrade thise number a bit. Like, to 256MB. But 512
is pretty high And 800MB is even more.
Big memstores takes more time to get flush and can block the writes if they
are not fast enough. If
Correction:
4. WAL is rolling prematurely, controlled by hbase.regionserver.maxlogs
and dfs.block.size.
Should read:
4. WAL is rolling, controlled by hbase.regionserver.maxlogs and
dfs.block.size.
-Vlad
On Mon, Aug 24, 2015 at 10:36 AM, Ted Yu yuzhih...@gmail.com wrote:
Related please
