[
https://issues.apache.org/jira/browse/HBASE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624769#comment-13624769
]
Jeffrey Zhong commented on HBASE-7824:
--------------------------------------
I pasted the whole related code snippet as below. Ram's suggestion is possible
because no one re-assign META till assignmentManager.assignMeta(). The modified
logic is same as before the patch.
{code}
...
ServerName currentMetaServer =
this.catalogTracker.getMetaLocationOrReadLocationFromRoot();
if (currentMetaServer != null &&
!currentMetaServer.equals(previousRootServer)) {
fileSystemManager.splitAllLogs(currentMetaServer);
if (this.serverManager.isServerOnline(currentMetaServer)) {
this.serverManager.expireServer(currentMetaServer);
}
}
assignmentManager.assignMeta();
enableSSHandWaitForMeta();
...
{code}
> Improve master start up time when there is log splitting work
> -------------------------------------------------------------
>
> Key: HBASE-7824
> URL: https://issues.apache.org/jira/browse/HBASE-7824
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 0.94.8
>
> Attachments: hbase-7824.patch, hbase-7824_v2.patch,
> hbase-7824_v3.patch, hbase-7824-v7.patch, hbase-7824-v8.patch
>
>
> When there is log split work going on, master start up waits till all log
> split work completes even though the log split has nothing to do with meta
> region servers.
> It's a bad behavior considering a master node can run when log split is
> happening while its start up is blocking by log split work.
> Since master is kind of single point of failure, we should start it ASAP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
