hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17943) The in-memory flush size is different for each CompactingMemStore located in the same region
Date Fri, 21 Apr 2017 03:23:04 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chia-Ping Tsai updated HBASE-17943:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks for the reviews. [~yuzhihong@gmail.com], [~anoop.hbase], and [~ram_krish]

> 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)

Mime
View raw message