Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Jul 2016 03:55:11 +0000 (UTC)
From: "Yu Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12987538.1467910612000.54490.1467950111015@Atlassian.JIRA>
In-Reply-To: <JIRA.12987538.1467910612000@Atlassian.JIRA>
References: <JIRA.12987538.1467910612000@Atlassian.JIRA> <JIRA.12987538.1467910612267@arcas>
Subject: [jira] [Updated] (HBASE-16195) Should not add chunk into chunkQueue
 if not using chunk pool in HeapMemStoreLAB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 08 Jul 2016 03:55:17 -0000


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

Yu Li updated HBASE-16195:
--------------------------
    Attachment: HBASE-16195.patch

The initial patch:
1. Change to only initialize and use chunkQueue when chunkPool is in use.
2. Limit chunkQueue length, max allowed memory taken by chunk queue is memstore flush size by default. Introduced property {{hbase.hregion.memstore.mslab.chunkqueue.length}} to set it.
3. Remove the chunk from chunkQueue after retiring it. Notice that chunkPool might be full in which case the {{putbackChunks}} call won't be able to clear chunkQueue, so we should remove the chunk explicitly.

> Should not add chunk into chunkQueue if not using chunk pool in HeapMemStoreLAB
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-16195
>                 URL: https://issues.apache.org/jira/browse/HBASE-16195
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Yu Li
>            Assignee: Yu Li
>         Attachments: HBASE-16195.patch
>
>
> Problem description and analysis please refer to HBASE-16193


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