[
https://issues.apache.org/jira/browse/HBASE-17902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971312#comment-15971312
]
Hudson commented on HBASE-17902:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #145 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/145/])
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
> Backport HBASE-16367 "Race between master and region server initialization
> may lead to premature server abort" to 1.3
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-17902
> URL: https://issues.apache.org/jira/browse/HBASE-17902
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 1.3.2
>
> Attachments: 17902.branch-1.3.txt
>
>
> This is to fix the case where hbase master always dies shortly after start.
> 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.
> branch-1.3 has been in quiet mode leading up to the release of 1.3.1
> Once 1.3.1 is released, the fix can go into branch-1.3
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
