hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Fri, 11 Nov 2016 05:16:58 GMT

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

Anoop Sam John commented on HBASE-16417:
----------------------------------------

bq. I did a mistake when running data compaction in previous rounds. I turned off the mslab
flag but did not remove the chunk pool parameters and as a result a chunk pool was allocated
but not used.
That is not fully ur mistake.  When MSLAB is turned off by config, even if there are pool
related configs present, we should not init the pool. This will never get used any way.  This
is the way it worked. Only in trunk this behave change happened. My bad. HBASE-16407 is the
culprit.  Raised HBASE-17071 to correct it in trunk.  Thanks for the nice find.

> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>
>                 Key: HBASE-16417
>                 URL: https://issues.apache.org/jira/browse/HBASE-16417
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Eshcar Hillel
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16417-benchmarkresults-20161101.pdf, HBASE-16417-benchmarkresults-20161110.pdf
>
>




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

Mime
View raw message