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 665C7F3FC for ; Thu, 4 Apr 2013 03:03:19 +0000 (UTC) Received: (qmail 8738 invoked by uid 500); 4 Apr 2013 03:03:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 8702 invoked by uid 500); 4 Apr 2013 03:03:18 -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 8687 invoked by uid 99); 4 Apr 2013 03:03:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 03:03:18 +0000 Date: Thu, 4 Apr 2013 03:03:18 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8259) Snapshot backport in 0.94.6 breaks rolling restarts 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-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621691#comment-13621691 ] Lars Hofhansl commented on HBASE-8259: -------------------------------------- This makes me want to release 0.94.7 soon. > Snapshot backport in 0.94.6 breaks rolling restarts > --------------------------------------------------- > > Key: HBASE-8259 > URL: https://issues.apache.org/jira/browse/HBASE-8259 > Project: HBase > Issue Type: Bug > Affects Versions: 0.94.6 > Reporter: Jean-Daniel Cryans > Assignee: Matteo Bertozzi > Priority: Blocker > Fix For: 0.94.7 > > Attachments: HBASE-8259-v0.patch > > > [~aleksshulman] found with his nifty QA tools that 0.94.6 has an incompatible change due to HBASE-7360 (Snapshot 0.94 Backport) that breaks rolling restarts. > RegionTransitionData.write() uses eventType.ordinal() that is the index in the enum and not the value specified in the enum definition. It means we can't add new states in the middle of the list. This can be fixed by moving C_M_SNAPSHOT_TABLE and C_M_RESTORE_SNAPSHOT at the end of the list. Trunk does the right thing already. > Right now, RIT znodes created with 0.94.6 (or top of the branch) will use the wrong value for the event type. You will see things like: > {noformat} > 2013-04-03 14:57:25,197 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: regionserver:60020-0x13dd1e10dbd0004 Attempting to transition node 70236052/-ROOT- from M_ZK_REGION_OFFLINE to RS_ZK_REGION_OPENING > 2013-04-03 14:57:25,201 WARN org.apache.hadoop.hbase.zookeeper.ZKAssign: regionserver:60020-0x13dd1e10dbd0004 Attempt to transition the unassigned node for 70236052 from M_ZK_REGION_OFFLINE to RS_ZK_REGION_OPENING failed, the node existed but was in the state M_SERVER_SHUTDOWN set by the server 192.168.1.112,60020,1365026237977 > 2013-04-03 14:57:25,201 WARN org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Failed transition from OFFLINE to OPENING for region=70236052 > 2013-04-03 14:57:25,201 WARN org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler: Region was hijacked? It no longer exists, encodedName=70236052 > {noformat} > We should roll a 0.94.6.1 or 0.94.7 as soon this is fixed IMO. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira