[
https://issues.apache.org/jira/browse/HBASE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689053#action_12689053
]
stack commented on HBASE-1008:
------------------------------
J-D, this patch reads all edits into memory. I suppose thats OK? IIRC, the
log is rotated after N edits rather than after its grown to a particular size.
If the log individual edits are very large, we could blow out the heap?
Currently number of threads == number of regions in particular commit log?
You might try setting bigger buffer on SequenceFile.Reader? Might make things
run faster.
> [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
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: 1008-v2.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.
