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 2016/08/06 09:21:20 UTC
[jira] [Updated] (HBASE-16367) Race between master and region
server initialization may lead to premature server abort
[ https://issues.apache.org/jira/browse/HBASE-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-16367:
---------------------------
Affects Version/s: 1.1.2
> 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
>
> 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.
> {code}
> this.oldLogDir = createInitialFileSystemLayout();
> HFileSystem.addLocationsOrderInterceptor(conf);
> LOG.info("creating splitLogManager");
> {code}
> 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.4#6332)