hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8434) Allow enabling hbase 8354 to support real lease recovery
Date Thu, 27 Jun 2013 04:47:22 GMT

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

Varun Sharma commented on HBASE-8434:

HBASE 8670 is a backport for HBASE 8449 which refactors lease recovery retries in wake of
findings in HBASE 8389. 

In HBase 8389, we basically decided to give up lease recovery for 0.94 and accept data loss.
The reason for giving up lease recovery was because it required a whole bunch of timeouts
to fit in nicely or else you could have infinite race conditions and a super long recovery
from region server failures. HBASE 8449 tried to fix it by refactoring these retries and timeouts
a little bit and HBASE 8670 is trying to backport that refactoring.

On the other hand, this one is a simple change which is allowing us to enable mandatory lease
recovery through a config parameter who care about their data but also requires them to run
with appropriate timeouts.

I agree that this is not required for 0.94 but otherwise we may have data loss.
> 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.10
>         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