[ https://issues.apache.org/jira/browse/HBASE-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971305#comment-15971305 ]
Hudson commented on HBASE-16367: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #157 (See [https://builds.apache.org/job/HBase-1.3-JDK8/157/]) HBASE-17902 Backport HBASE-16367 "Race between master and region server (tedyu: rev 0e95c8156ac5ac507827ff5eb4504a42fa22b454) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Race between master and region server initialization may lead to premature > server abort > --------------------------------------------------------------------------------------- > > Key: HBASE-16367 > URL: https://issues.apache.org/jira/browse/HBASE-16367 > Project: HBase > Issue Type: Bug > Affects Versions: 1.1.2 > Reporter: Ted Yu > Assignee: Ted Yu > Fix For: 2.0.0, 1.4.0 > > Attachments: 16367.addendum, 16367.v1.txt, 16367.v2.txt, > 16367.v3.txt, 63908-master.log > > > I was troubleshooting a case where hbase (1.1.2) master always dies shortly > after start - see attached master log snippet. > It turned out that master initialization thread was racing with > HRegionServer#preRegistrationInitialization() (initializeZooKeeper, actually) > since HMaster extends HRegionServer. > Through additional logging in master: > {code} > this.oldLogDir = createInitialFileSystemLayout(); > HFileSystem.addLocationsOrderInterceptor(conf); > LOG.info("creating splitLogManager"); > {code} > I found that execution didn't reach the last log line before region server > declared cluster Id being null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)