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

Hudson commented on HBASE-17071:
--------------------------------

ABORTED: Integrated in Jenkins build HBase-Trunk_matrix #1945 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1945/])
HBASE-17071 Do not initialize MemstoreChunkPool when use mslab option is 
(anoopsamjohn: rev fa838b020df0235e9bea448730b3bd034e9bfb65)
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMemStoreChunkPool.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreChunkPool.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreLAB.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCellFlatSet.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SegmentFactory.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactingMemStore.java


> Do not initialize MemstoreChunkPool when use mslab option is turned off
> -----------------------------------------------------------------------
>
>                 Key: HBASE-17071
>                 URL: https://issues.apache.org/jira/browse/HBASE-17071
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17071.patch
>
>
> This is a 2.0 only issue and induced by HBASE-16407. 
> We are initializing MSLAB chunk pool along with RS start itself now. (To pass 
> it as a HeapMemoryTuneObserver).
> When MSLAB is turned off  (ie. hbase.hregion.memstore.mslab.enabled is 
> configured false) we should not be initializing MSLAB chunk pool at all.  By 
> default the initial chunk count to be created will be 0 only.  Still better 
> to avoid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to