Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Jan 2015 23:14:35 +0000 (UTC)
From: "Esteban Gutierrez (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12752121.1414799960000.32966.1420672475943@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=14268478#comment-14268478 ] 

Esteban Gutierrez commented on HBASE-12405:
-------------------------------------------

Ok, probably it won't make any difference since the message should be the same but now is handled by ClusterStatus.

> 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.patch, HBASE-12405_1.patch, HBASE-12405_2.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)