[
https://issues.apache.org/jira/browse/HBASE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592434#comment-13592434
]
Jeffrey Zhong commented on HBASE-7824:
--------------------------------------
The reason to add those previous dead non-meta region servers into deadServers
is to let the new master instance start as a failover such as the following
code in AssignmentManager. In addition, we don't want AM assign those regions
before log splitting work complete that's why let AM skip them inside function
processDeadServersAndRegionsInTransition but handle them in SSH.
{code}
if (!this.serverManager.getDeadServers().isEmpty()) {
this.failover = true;
}
{code}
Since those failed servers will be processed by SSH so their regions should be
online and I did see test log message "Finished processing of shutdown".
There are couple of regions aren't assigned for some reason and I need to dig
more in the test case and keep you updated.
Thanks,
-Jeffrey
> 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
