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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/03 01:04:00 UTC

[jira] [Commented] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

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

Andrew Purtell commented on HBASE-13200:
----------------------------------------

Sorry I'm a bit behind [~liushaohui]. Looks ok for 0.98, would also need to go in on branch-1 and branch-1.0. 

> Improper configuration can leads to endless lease recovery during failover
> --------------------------------------------------------------------------
>
>                 Key: HBASE-13200
>                 URL: https://issues.apache.org/jira/browse/HBASE-13200
>             Project: HBase
>          Issue Type: Bug
>          Components: MTTR
>            Reporter: He Liangliang
>            Assignee: He Liangliang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13200.patch
>
>
> When a node (DN+RS) has machine/OS level failure, another RS will try to do lease recovery for the log file. It will retry for every hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When the hdfs configuration is not properly configured (e.g. socket connection timeout) and without patch HDFS-4721, the lease recovery time can exceeded the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)