[
https://issues.apache.org/jira/browse/HBASE-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657680#comment-13657680
]
stack commented on HBASE-7006:
------------------------------
[~jeffreyz] The 'next steps' are to be done in other issues, not on this one?
Have you run the IntegrationTestBigLinkedList with this in place killing
servers as it runs? I am game for checking it in. It has a good bit of review
and if we have not found egregious error by now, then we get what we deserve.
Nice one.
> [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.95.1
>
> Attachments: 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, 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.
> Distributed Log Replay Description:
> After a region server fails, we firstly assign a failed region to another
> region server with recovering state marked in ZooKeeper. Then a
> SplitLogWorker directly replays edits from WAL(Write-Ahead-Log)s of the
> failed region server to the region after it's re-opened in the new location.
> When a region is in recovering state, it can also accept writes but no
> reads(including Append and Increment), region split or merge.
> The feature piggybacks on existing distributed log splitting framework and
> directly replay WAL edits to another region server instead of creating
> recovered.edits files.
> The advantages over existing log splitting recovered edits implementation:
> 1) Eliminate the steps to write and read recovered.edits files. There could
> be thousands of recovered.edits files are created and written concurrently
> during a region server recovery. Many small random writes could degrade the
> overall system performance.
> 2) Allow writes even when a region is in recovering state. It only takes
> seconds for a failed over region to accept writes again.
> The feature can be disabled by setting hbase.master.distributed.log.replay to
> false(by default is true)
--
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
