Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 17 Nov 2014 19:29:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12752121.1414799960000.517158.1416252574457@Atlassian.JIRA>
In-Reply-To: <JIRA.12752121.1414799960000@Atlassian.JIRA>
References: <JIRA.12752121.1414799960000@Atlassian.JIRA>
 <JIRA.12752121.1414799960940@arcas>
Subject: [jira] [Resolved] (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:all-tabpanel ]

stack resolved HBASE-12405.
---------------------------
    Resolution: Duplicate

Dup of HBASE-10201 at [~Apache9]'s request

> WAL accounting by Store
> -----------------------
>
>                 Key: HBASE-12405
>                 URL: https://issues.apache.org/jira/browse/HBASE-12405
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: zhangduo
>            Assignee: zhangduo
>
> 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)