You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/04/11 15:35:42 UTC
[jira] [Created] (HBASE-17902) Backport HBASE-16367 "Race between
master and region server initialization may lead to premature server abort"
to 1.3
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)