hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17943) The in-memory flush size is different for each CompactingMemStore located in the same region
Date Sun, 30 Apr 2017 22:25:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990453#comment-15990453
] 

Hudson commented on HBASE-17943:
--------------------------------

ABORTED: Integrated in Jenkins build HBase-HBASE-14614 #190 (See [https://builds.apache.org/job/HBase-HBASE-14614/190/])
HBASE-17943 The in-memory flush size is different for each (chia7712: rev ea3a27b18df875284899b04fbc5fb58a3120e6c7)
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestWalAndCompactingMemStoreFlush.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactingMemStore.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionServicesForStores.java
HBASE-17943 Addendum increases the threshold value of in-memory (chia7712: rev 9053ec6fe6505eba4f14adfdd83329511e4a77f0)
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestWalAndCompactingMemStoreFlush.java


> 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.addendum.patch, 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