Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 19 Mar 2015 02:15:38 +0000 (UTC)
From: "Liu Shaohui (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12781153.1426075283000.139061.1426731338620@Atlassian.JIRA>
In-Reply-To: <JIRA.12781153.1426075283000@Atlassian.JIRA>
References: <JIRA.12781153.1426075283000@Atlassian.JIRA>
 <JIRA.12781153.1426075283273@arcas>
Subject: [jira] [Commented] (HBASE-13200) Improper configuration can leads
 to endless lease recovery during failover
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Liu Shaohui commented on HBASE-13200:
-------------------------------------

[~apurtell]
Do you like this to 0.98?

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