Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 10 Mar 2016 22:26:40 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12948912.1457645369000.63187.1457648800736@Atlassian.JIRA>
In-Reply-To: <JIRA.12948912.1457645369000@Atlassian.JIRA>
References: <JIRA.12948912.1457645369000@Atlassian.JIRA>
 <JIRA.12948912.1457645369786@arcas>
Subject: [jira] [Updated] (HBASE-15441) Fix WAL splitting when region has
 moved multiple times
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-15441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliott Clark updated HBASE-15441:
----------------------------------
    Description: 
Currently WAL splitting is broken when a region has been opened multiple times in recent minutes.

Region open and region close write event markers to the wal. These markers should have the sequence id in them. However it is currently getting 1. That means that if a region has moved multiple times in the last few mins then multiple split log workers will try and create the recovered edits file for sequence id 1. One of the workers will fail and on failing they will delete the recovered edits. Causing all split wal attempts to fail.

We need to:
# make sure that close get the correct sequence id for open.
# Filter all region events from recovered edits


It appears that the close event with a sequence id of one is coming from region warm up.

  was:
Currently WAL splitting is broken when a region has been opened multiple times in recent minutes.

Region open and region close write event markers to the wal. These markers should have the sequence id in them. However it is currently getting 1. That means that if a region has moved multiple times in the last few mins then multiple split log workers will try and create the recovered edits file for sequence id 1. One of the workers will fail and on failing they will delete the recovered edits. Causing all split wal attempts to fail.

We need to:
# make sure that open and close get the correct sequence id for open.
# Filter all region events from recovered edits


> Fix WAL splitting when region has moved multiple times
> ------------------------------------------------------
>
>                 Key: HBASE-15441
>                 URL: https://issues.apache.org/jira/browse/HBASE-15441
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Elliott Clark
>            Priority: Blocker
>
> Currently WAL splitting is broken when a region has been opened multiple times in recent minutes.
> Region open and region close write event markers to the wal. These markers should have the sequence id in them. However it is currently getting 1. That means that if a region has moved multiple times in the last few mins then multiple split log workers will try and create the recovered edits file for sequence id 1. One of the workers will fail and on failing they will delete the recovered edits. Causing all split wal attempts to fail.
> We need to:
> # make sure that close get the correct sequence id for open.
> # Filter all region events from recovered edits
> It appears that the close event with a sequence id of one is coming from region warm up.


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