hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1008) [performance] The replay of logs on server crash takes way too long
Date Wed, 13 May 2009 16:07:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708984#action_12708984
] 

Jean-Daniel Cryans commented on HBASE-1008:
-------------------------------------------

Sounds great. Just to be sure that I understand what you wrote, you basically think that we
should reverse the way the latest patch works? Multi threaded reads and a single writer?

> [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.


Mime
View raw message