Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 10 Mar 2015 09:32:38 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12752121.1414799960000.49387.1425979958721@Atlassian.JIRA>
In-Reply-To: <JIRA.12752121.1414799960000@Atlassian.JIRA>
References: <JIRA.12752121.1414799960000@Atlassian.JIRA>
 <JIRA.12752121.1414799960940@arcas>
Subject: [jira] [Commented] (HBASE-12405) WAL accounting by Store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354593#comment-14354593 ] 

Hudson commented on HBASE-12405:
--------------------------------

SUCCESS: Integrated in HBase-TRUNK #6232 (See [https://builds.apache.org/job/HBase-TRUNK/6232/])
HBASE-12405 addendum fix HRegion heap size (zhangduo: rev 105f9b328221eef30c61a36593927be9a61200b7)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java


> WAL accounting by Store
> -----------------------
>
>                 Key: HBASE-12405
>                 URL: https://issues.apache.org/jira/browse/HBASE-12405
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>    Affects Versions: 2.0.0, 1.1.0
>            Reporter: zhangduo
>            Assignee: zhangduo
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-12405-addendum.patch, HBASE-12405.patch, HBASE-12405_1.patch, HBASE-12405_2.patch, HBASE-12405_3.patch, HBASE-12405_4.patch, HBASE-12405_5.patch
>
>
> HBASE-10201 has made flush decisions per Store, but has not done enough work on HLog, so there are two problems:
> 1. We record minSeqId both in HRegion and FSHLog, which is a duplication.
> 2. There maybe holes in WAL accounting.
>     For example, assume family A with sequence id 1 and 3, family B with seqId 2. If we flush family A, we can only record that WAL before sequence id 1 can be removed safely. If we do a replay at this point, sequence id 3 will also be replayed which is unnecessary.


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