hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8434) Allow enabling hbase 8354 to support real lease recovery
Date Fri, 03 May 2013 17:54:16 GMT

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

Nicolas Liochon commented on HBASE-8434:

I proposed this in HBASE-8389:
I see a possible common implementation (trunk / hbase 0.94)
    if HDFS-4754, calls markAsStale to be sure this datanode won't be used.
    call recoverFileLease a first time
    if HDFS-4525 is available, call isFileClosed every second to detect that the recovery
is done
    every 60s, call again recoverFileLease (either isFileClosed is missing, either we went
into one of the bad scenario above).

This would mean: no dataloss and a MTTR of:
    less than a minute if we have stale mode + HDFS-4721 + HDFS-4754 + HDFS-4525 + no retry
in HDFS recoverLease or Varun's settings.
    around 12 minutes if we have none of the above. But that's what we have already without
the stale mode imho.
    in the middle if we have a subset of the above patches and config.

What do you think?

> Allow enabling hbase 8354 to support real lease recovery
> --------------------------------------------------------
>                 Key: HBASE-8434
>                 URL: https://issues.apache.org/jira/browse/HBASE-8434
>             Project: HBase
>          Issue Type: Improvement
>          Components: MTTR
>            Reporter: Varun Sharma
>            Assignee: Varun Sharma
>             Fix For: 0.94.8
>         Attachments: 8434.patch
> Please see discussion in HBase 8389.
> For environments where lease recovery time can be bounded on the HDFS side through tight
timeouts, provide a toggle for users who want the WAL splitting to continue only after the
lease is truly recovered and the file is closed.

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

View raw message