Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C95B31003C for ; Fri, 11 Oct 2013 23:32:42 +0000 (UTC) Received: (qmail 19211 invoked by uid 500); 11 Oct 2013 23:32:42 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 19186 invoked by uid 500); 11 Oct 2013 23:32:42 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 19177 invoked by uid 99); 11 Oct 2013 23:32:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Oct 2013 23:32:42 +0000 Date: Fri, 11 Oct 2013 23:32:42 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793134#comment-13793134 ] Hudson commented on HBASE-9696: ------------------------------- SUCCESS: Integrated in hbase-0.96-hadoop2 #85 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/85/]) HBASE-9696 Master recovery ignores online merge znode (jxiang: rev 1531434) * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/executor/EventType.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/master/RegionState.java * /hbase/branches/0.96/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/actions/SplitRandomRegionOfTableAction.java * /hbase/branches/0.96/hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/ClusterStatusProtos.java * /hbase/branches/0.96/hbase-protocol/src/main/protobuf/ClusterStatus.proto * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/MergedRegionHandler.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/SplitRegionHandler.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionMergeTransaction.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMaster.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java > 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.0 > > Attachments: 0.96-9696_v3.2.patch, 0.96-9696_v3.3.patch, trunk-9696.patch, trunk-9696_v2.1.patch, trunk-9696_v2.patch, trunk-9696_v3.1.patch, trunk-9696_v3.2.patch, trunk-9696_v3.3.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)