Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 11 Oct 2013 06:54:42 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12671688.1380668169104.50322.1381474482256@arcas>
In-Reply-To: <JIRA.12671688.1380668169104@arcas>
References: <JIRA.12671688.1380668169104@arcas>
Subject: [jira] [Commented] (HBASE-9696) Master recovery ignores online
 merge znode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-9696:
------------------------------

I rechecked.  The MERGING znode actually has the name of the merged region so my claim above that PENDING_MERGE having name of merging region being new is not totally correct.

> Master recovery ignores online merge znode
> ------------------------------------------
>
>                 Key: HBASE-9696
>                 URL: https://issues.apache.org/jira/browse/HBASE-9696
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Region Assignment
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 0.98.0, 0.96.1
>
>         Attachments: trunk-9696.patch, trunk-9696_v2.1.patch, trunk-9696_v2.patch, trunk-9696_v3.patch, trunk-9696_v3.patch
>
>
> The online merge znode uses the new region to be created.  When master restarts, the new region is still unknown if the merging is not completed. Therefore the znode is ignored, which should not.  That means the two merging regions could be moved around.  This could cause some data loss if we are not luck.


--
This message was sent by Atlassian JIRA
(v6.1#6144)