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 CDD0590DD for ; Wed, 25 Apr 2012 11:42:29 +0000 (UTC) Received: (qmail 45292 invoked by uid 500); 25 Apr 2012 11:42:29 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 45248 invoked by uid 500); 25 Apr 2012 11:42:29 -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 45233 invoked by uid 99); 25 Apr 2012 11:42:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 11:42:29 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 11:42:26 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id D937540E960 for ; Wed, 25 Apr 2012 11:42:05 +0000 (UTC) Date: Wed, 25 Apr 2012 11:42:05 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: <174669392.390.1335354125891.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <584055330.915.1334972612554.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-5849) On first cluster startup, RS aborts if root znode is not available 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-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261475#comment-13261475 ] Hudson commented on HBASE-5849: ------------------------------- Integrated in HBase-0.92 #390 (See [https://builds.apache.org/job/HBase-0.92/390/]) HBASE-5849 On first cluster startup, RS aborts if root znode is not available; REAPPLY (Revision 1330119) HBASE-5849 On first cluster startup, RS aborts if root znode is not available; REAPPLY (Revision 1330118) Result = FAILURE stack : Files : * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/TestClusterBootOrder.java stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java > On first cluster startup, RS aborts if root znode is not available > ------------------------------------------------------------------ > > Key: HBASE-5849 > URL: https://issues.apache.org/jira/browse/HBASE-5849 > Project: HBase > Issue Type: Bug > Components: master, regionserver, zookeeper > Affects Versions: 0.92.2, 0.96.0, 0.94.1 > Reporter: Enis Soztutar > Assignee: Enis Soztutar > Fix For: 0.92.2, 0.94.0 > > Attachments: 5849v3.txt, HBASE-5849_v1.patch, HBASE-5849_v2.patch, HBASE-5849_v4-0.92.patch, HBASE-5849_v4.patch, HBASE-5849_v4.patch, HBASE-5849_v4.patch > > > When launching a fresh new cluster, the master has to be started first, which might create race conditions for starting master and rs at the same time. > Master startup code is smt like this: > - establish zk connection > - create root znodes in zk (/hbase) > - create ephemeral node for master /hbase/master, > Region server start up code is smt like this: > - establish zk connection > - check whether the root znode (/hbase) is there. If not, shutdown. > - wait for the master to create znodes /hbase/master > So, the problem is on the very first launch of the cluster, RS aborts to start since /hbase znode might not have been created yet (only the master creates it if needed). Since /hbase/ is not deleted on cluster shutdown, on subsequent cluster starts, it does not matter which order the servers are started. So this affects only first launchs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira