[
https://issues.apache.org/jira/browse/HBASE-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259983#comment-13259983
]
Hadoop QA commented on HBASE-5849:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523865/HBASE-5849_v1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 3 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks
org.apache.hadoop.hbase.util.TestProcessBasedCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1617//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1617//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1617//console
This message is automatically generated.
> 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
> Attachments: HBASE-5849_v1.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
