[
https://issues.apache.org/jira/browse/HBASE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592009#comment-13592009
]
ramkrishna.s.vasudevan commented on HBASE-7824:
-----------------------------------------------
@Jeff
Any specific reason for adding the server to be processed (other than RS
carrying ROOT or META) to the deadServers.
{code}
void processDeadServer(final ServerName serverName) {
this.deadservers.add(serverName);
this.services.getExecutorService().submit(
new ServerShutdownHandler(this.master, this.services, this.deadservers,
serverName, true));
}
{code}
I remember we used to track the servers that got expired when master was coming
up using deadServers. See ServerManager.expireServer().
May be some specific issues you got?
> 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.6
>
> Attachments: hbase-7824.patch, hbase-7824_v2.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
