[
https://issues.apache.org/jira/browse/HBASE-17943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976391#comment-15976391
]
Chia-Ping Tsai commented on HBASE-17943:
----------------------------------------
bq. How u found it? Doing any testing with CompactingMemstore?
I'm investigating the TestAcidGuarantees, and I notice the following log
message.
{noformat}
regionserver.CompactingMemStore(113): Setting in-memory flush size threshold to
32768
regionserver.CompactingMemStore(113): Setting in-memory flush size threshold to
16384
regionserver.CompactingMemStore(113): Setting in-memory flush size threshold to
8192
{noformat}
> The in-memory flush size is different for each CompactingMemStore located in
> the same region
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-17943
> URL: https://issues.apache.org/jira/browse/HBASE-17943
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 2.0.0
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Fix For: 2.0.0
>
> Attachments: HBASE-17943.v0.patch
>
>
> {noformat}
> private void initInmemoryFlushSize(Configuration conf) {
> long memstoreFlushSize = getRegionServices().getMemstoreFlushSize();
> int numStores = getRegionServices().getNumStores();
> if (numStores <= 1) {
> // Family number might also be zero in some of our unit test case
> numStores = 1;
> }
> inmemoryFlushSize = memstoreFlushSize / numStores;
> {noformat}
> We initialize each store in parallel, so the return value from getNumStores()
> may be different for each CompactingMemStore.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
