You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/11/19 19:56:44 UTC

[jira] Updated: (HBASE-1008) [performance] The replay of logs on server crash takes way too long

     [ https://issues.apache.org/jira/browse/HBASE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1008:
-------------------------

    Fix Version/s:     (was: 0.20.0)
                   0.19.0

As is, this replay stuff is unacceptable.  Moving into 0.19.0.

Replay is slowing down with time.

Replay is not even multithread -- runs in series.

If master is shutdown during replay, looks like we lose edits (the region files will not be closed).

> [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: Critical
>             Fix For: 0.19.0
>
>
> 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.