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 7A6141868A for ; Fri, 15 Jan 2016 04:47:40 +0000 (UTC) Received: (qmail 95009 invoked by uid 500); 15 Jan 2016 04:47:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 94957 invoked by uid 500); 15 Jan 2016 04:47: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 94933 invoked by uid 99); 15 Jan 2016 04:47:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2016 04:47:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CF3EA2C14F7 for ; Fri, 15 Jan 2016 04:47:39 +0000 (UTC) Date: Fri, 15 Jan 2016 04:47:39 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14969) Add throughput controller for flush 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-14969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101186#comment-15101186 ] Ted Yu commented on HBASE-14969: -------------------------------- For NoLimitThroughputController : {code} 44 private volatile boolean stopped; {code} Does the field have to be volatile ? I don't see synchronization around access to the field. {code} 33 *
  • In normal case, the max throughput is tune between {code} 'is tune' -> 'is tuned' > Add throughput controller for flush > ----------------------------------- > > Key: HBASE-14969 > URL: https://issues.apache.org/jira/browse/HBASE-14969 > Project: HBase > Issue Type: Improvement > Affects Versions: 2.0.0 > Reporter: Yu Li > Assignee: Yu Li > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-14969.patch, HBASE-14969_v2.patch, HBASE-14969_v3.patch, HBASE-14969_v4.patch > > > In HBASE-8329 we added a throughput controller for compaction, to avoid spike caused by huge IO pressure like network/disk overflow. However, even with this control on, we are still observing disk utils near 100%, and by analysis we think this is caused by flush, especially when we increase the setting of {{hbase.hstore.flusher.count}} > In this JIRA, we propose to add throughput control feature for flush, as a supplement of HBASE-8329 to better control IO pressure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)