hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5843) Improve HBase MTTR - Mean Time To Recover
Date Thu, 13 Sep 2012 14:12:09 GMT

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

nkeywal commented on HBASE-5843:
--------------------------------

Test with meta:

On a real cluster, 3 nodes.
    dfs.replication = 2
    local HD.
    Start with 2 DN and 2 RS. Create a table with 100 regions in the second one. The first
holds meta & root.
    Start another box with a DN and a RS. This box is empty (no regions, no blocks).
    Unplug the box with meta & root.
    try to create a table

=> Time taken is the recovery time of the bow holding meta. No bad surprise. It means as
well that with the default zookeeper timeout you're loosing the cluster for 3 minutes if your
meta regionserver dies. HBASE-6772, HBASE-6773 and HBASE-6774 would help to increase meta
failure resiliency.

                
> Improve HBase MTTR - Mean Time To Recover
> -----------------------------------------
>
>                 Key: HBASE-5843
>                 URL: https://issues.apache.org/jira/browse/HBASE-5843
>             Project: HBase
>          Issue Type: Umbrella
>    Affects Versions: 0.96.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>
> A part of the approach is described here: https://docs.google.com/document/d/1z03xRoZrIJmg7jsWuyKYl6zNournF_7ZHzdi0qz_B4c/edit
> The ideal target is:
> - failure impact client applications only by an added delay to execute a query, whatever
the failure.
> - this delay is always inferior to 1 second.
> We're not going to achieve that immediately...
> Priority will be given to the most frequent issues.
> Short term:
> - software crash
> - standard administrative tasks as stop/start of a cluster.

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

Mime
View raw message