[
https://issues.apache.org/jira/browse/HBASE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708998#action_12708998
]
stack commented on HBASE-1008:
------------------------------
I've changed my mind after reading this patch. This patch looks great and the
amount of splitting processed above -- 3M in ~90seconds -- is good next place
to go regards log recovery.
+1 on commit but make the upper bound on threads a configuration (doesn't have
to be in hadoop-default.xml -- let fellas read code to find it).
Meantime, I'll go work elsewhere on bounding size of logs so what shows up in
splitlog can be expected to be of reasonable size -- not of a size that will
blow out mem.
> [performance] The replay of logs on server crash takes way too long
> -------------------------------------------------------------------
>
> Key: HBASE-1008
> URL: https://issues.apache.org/jira/browse/HBASE-1008
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Assignee: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: 1008-v2.patch, hbase-1008-3.patch
>
>
> Watching recovery from a crash on streamy.com where there were 1048 logs and
> repay is running at rate of about 20 seconds each. Meantime these regions
> are not online. This is way too long to wait on recovery for a live site.
> Marking critical. Performance related so priority and in 0.20.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
