hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-17902) Backport HBASE-16367 "Race between master and region server initialization may lead to premature server abort" to 1.3
Date Tue, 11 Apr 2017 15:35:42 GMT
Ted Yu created HBASE-17902:
------------------------------

             Summary: 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
             Fix For: 1.3.2


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)

Mime
View raw message