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 697EA9DBD for ; Mon, 10 Sep 2012 16:48:10 +0000 (UTC) Received: (qmail 82021 invoked by uid 500); 10 Sep 2012 16:48:10 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 81968 invoked by uid 500); 10 Sep 2012 16:48:10 -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 81920 invoked by uid 99); 10 Sep 2012 16:48:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Sep 2012 16:48:09 +0000 Date: Tue, 11 Sep 2012 03:48:09 +1100 (NCT) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: <662712484.58456.1347295689934.JavaMail.jiratomcat@arcas> In-Reply-To: <869539163.52135.1347050407882.JavaMail.jiratomcat@arcas> Subject: [jira] [Assigned] (HBASE-6745) Always flush region based on memstore size could hold hlog files from archiving 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-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang reassigned HBASE-6745: ---------------------------------- Assignee: Jimmy Xiang > Always flush region based on memstore size could hold hlog files from archiving > ------------------------------------------------------------------------------- > > Key: HBASE-6745 > URL: https://issues.apache.org/jira/browse/HBASE-6745 > Project: HBase > Issue Type: Bug > Components: replication, wal > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > > Currently, memstore flusher always chooses the biggest memstore region to flush. > Suppose I have two tables: one is very actively updated, while the other is periodically updated. The active one has biggest memstore all the time and is flushed all the time. But the in-active one never gets a chance to flush. Since it is not flushed, the hlog file can't be archived, although there are lots of hlog files. > If the active table happens to have big updates all the time, the hlog files could cause huge disk space pressure. > Other than the memstore size, periodically flushing regions based on hlog roll time is helpful in hlog archiving/replication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira