Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
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:
this.oldLogDir = createInitialFileSystemLayout(); HFileSystem.addLocationsOrderInterceptor(conf); LOG.info("creating splitLogManager");
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
Attachments
Attachments
Issue Links
- relates to
-
HBASE-16367 Race between master and region server initialization may lead to premature server abort
- Resolved