I noticed that parameter , But from the patch hbase-8163v6.patch which is changed for file MemStoreLAB.java , NOT file MemStoreChunkPool.java , so I was confused .
On 3 Jul 2019, at 19:27, Jean-Marc Spaggiari <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
I just checked and I can see it in 1.4.10
jmspaggiari@t460s:/stock/hbase-releases/hbase-1.4.10$ grep -R
final static String CHUNK_POOL_MAXSIZE_KEY =
Le mar. 2 juil. 2019 à 22:31, Vladimir Rodionov <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> a
HBase 1.4.10 should have MSLAB already. I presume. I personally have never
used 1.3.x and 1.4.x but I think if 1.1.x has this feature (its probably
there since 0.96?) 1.3 and 1.4 must have it as well.
On Mon, Jul 1, 2019 at 10:20 PM Syni Guo <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
I want to use MSLAB feature on Hbase 1.4.10, I checked the useage
) as bellow
, it was fixed 0.98.0, 0.95.0 and whether need to apply it on Hbase
Disable pool(default): configure
"hbase.hregion.memstore.chunkpool.maxsize" as 0
Enable pool: configure "hbase.hregion.memstore.chunkpool.maxsize" as a
percentage of global memstore size (between 0.0 and 1.0, recommend to set
it as the gap between min and max sizes of memstore, e.g. 0.5)
If you have a write-heavy workload, check out HBASE-8163
MemStoreChunkPool: An improvement for JAVA GC when using MSLAB<https://issues.apache.org/jira/browse/HBASE-8163>
. It describes
configurations to lower the amount of young GC during write-heavy
If you do not have HBASE-8163 installed,
1. Need to apply HBASE-8163 on Hbase 1.4.10 ?
2. How to check out HBASE-8163 is installed on Hbase 1.4.10 bin vaersion?