Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9442218C77 for ; Wed, 20 Jan 2016 03:45:40 +0000 (UTC) Received: (qmail 92031 invoked by uid 500); 20 Jan 2016 03:45:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 91967 invoked by uid 500); 20 Jan 2016 03:45:40 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 91910 invoked by uid 99); 20 Jan 2016 03:45:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2016 03:45:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EBC1B2C1F64 for ; Wed, 20 Jan 2016 03:45:39 +0000 (UTC) Date: Wed, 20 Jan 2016 03:45:39 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-15102) HeapMemoryTuner can "overtune" memstore size and suddenly drop it into blocking zone MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107935#comment-15107935 ] Hudson commented on HBASE-15102: -------------------------------- FAILURE: Integrated in HBase-Trunk_matrix #643 (See [https://builds.apache.org/job/HBase-Trunk_matrix/643/]) HBASE-15102 Fix HeapMemoryTuner overtuning memstore (eclark: rev 318814de28321a8a3d34cceea951bf164e3fa5af) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultHeapMemoryTuner.java * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHeapMemoryManager.java > HeapMemoryTuner can "overtune" memstore size and suddenly drop it into blocking zone > ------------------------------------------------------------------------------------ > > Key: HBASE-15102 > URL: https://issues.apache.org/jira/browse/HBASE-15102 > Project: HBase > Issue Type: Bug > Components: regionserver > Affects Versions: 2.0.0, 1.2.0, 1.3.0 > Reporter: Ashu Pachauri > Assignee: Ashu Pachauri > Priority: Critical > Fix For: 2.0.0, 1.2.0, 1.3.0 > > Attachments: HBASE-15102-V0.patch, HBASE-15102-V1.patch, HBASE-15102-V2.patch, HBASE-15102-V3.patch > > > DefaultHeapMemoryTuner often resets the maximum step size for tuning to 8% of total heap size. Often, when the size of memstore is to be decreased while tuning, the 8% tuning can suddenly drop the memstore size below the low water mark of the previous memstore size (which could potentially be the used size of the memstore) > This is problematic because suddenly it blocks all the updates by suddenly causing a situation where memstore used size is above high water mark. This has a very bad performance impact on an otherwise fine HBase cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)