[
https://issues.apache.org/jira/browse/HBASE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626232#comment-13626232
]
Jeffrey Zhong commented on HBASE-7824:
--------------------------------------
I'm about to send additional notes about DeadServer#cleanPreviousInstance. I
think it may help to solve all the confusions:
1) The above steps including AM#JoinCluster are before master.initialized
becomes true.
2) Inside function ServerManager#checkIsDead {code}
// remove dead server with same hostname and port of newly checking in rs
after master
// initialization.See HBASE-5916 for more information.
if ((this.services == null || ((HMaster) this.services).isInitialized())
&& this.deadservers.cleanPreviousInstance(serverName)) {
{code}
You can see this.deadservers.cleanPreviousInstance won't do anything because
master is NOT initialized yet.
> 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-v10.patch,
> hbase-7824_v2.patch, hbase-7824_v3.patch, hbase-7824-v7.patch,
> hbase-7824-v8.patch, hbase-7824-v9.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
