[
https://issues.apache.org/jira/browse/HBASE-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659801#comment-13659801
]
Jeffrey Zhong commented on HBASE-7006:
--------------------------------------
[~rajesh23] That's a bug before. Though we return false to break the
initialization but there is no return from caller finishInitialization so we
continue even master isn't initialized fully. The change is expecting
assignMeta to throw exception to stop master starts up.
{code}
finishInitialization(startupStatus, false);
loop();
{code}
> [MTTR] Improve Region Server Recovery Time - Distributed Log Replay
> -------------------------------------------------------------------
>
> Key: HBASE-7006
> URL: https://issues.apache.org/jira/browse/HBASE-7006
> Project: HBase
> Issue Type: New Feature
> Components: MTTR
> Reporter: stack
> Assignee: Jeffrey Zhong
> Priority: Critical
> Fix For: 0.98.0, 0.95.1
>
> Attachments: hbase-7006-addendum.patch, hbase-7006-combined.patch,
> hbase-7006-combined-v1.patch, hbase-7006-combined-v4.patch,
> hbase-7006-combined-v5.patch, hbase-7006-combined-v6.patch,
> hbase-7006-combined-v7.patch, hbase-7006-combined-v8.patch,
> hbase-7006-combined-v9.patch, LogSplitting Comparison.pdf,
> ProposaltoimprovelogsplittingprocessregardingtoHBASE-7006-v2.pdf
>
>
> Just saw interesting issue where a cluster went down hard and 30 nodes had
> 1700 WALs to replay. Replay took almost an hour. It looks like it could run
> faster that much of the time is spent zk'ing and nn'ing.
> Putting in 0.96 so it gets a look at least. Can always punt.
--
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
