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 B953E1869C for ; Sat, 27 Jun 2015 01:45:06 +0000 (UTC) Received: (qmail 20043 invoked by uid 500); 27 Jun 2015 01:45:05 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 19979 invoked by uid 500); 27 Jun 2015 01:45:05 -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 19725 invoked by uid 99); 27 Jun 2015 01:45:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2015 01:45:05 +0000 Date: Sat, 27 Jun 2015 01:45:05 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-13980) Distinguish blockedFlushCount vs unblockedFlushCount when tuning heap memory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Ted Yu created HBASE-13980: ------------------------------ Summary: Distinguish blockedFlushCount vs unblockedFlushCount when tuning heap memory Key: HBASE-13980 URL: https://issues.apache.org/jira/browse/HBASE-13980 Project: HBase Issue Type: Improvement Reporter: Ted Yu Priority: Minor Currently DefaultHeapMemoryTuner doesn't distinguish blockedFlushCount vs unblockedFlushCount. In its tune() method: {code} long totalFlushCount = blockedFlushCount+unblockedFlushCount; rollingStatsForCacheMisses.insertDataValue(cacheMissCount); rollingStatsForFlushes.insertDataValue(totalFlushCount); {code} Occurrence of blocked flush indicates that upper limit for memstore is not sufficient. We should either give blockedFlushCount more weight or, take tuning action based on blockedFlushCount directly. See discussion from tail of HBASE-13876. -- This message was sent by Atlassian JIRA (v6.3.4#6332)