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

Lars Hofhansl commented on HBASE-5849:
--------------------------------------

TestRegionRebalancing is unrelated (see HBASE-5848). TestReplication passes for 
me locally with v4 applied.
                
> 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

        

Reply via email to