From ebffc939ea06b8dd228eb4b74469f181c54d0c39 Mon Sep 17 00:00:00 2001
From: Michael Stack <stack@apache.org>
Date: Thu, 27 Jun 2013 17:23:01 +0000
Subject: [PATCH] HBASE-8813 Fix time b/w recoverLease invocations from HBASE
 8449

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1497465 13f79535-47bb-0310-9956-ffa450edef68
---
 hbase-common/src/main/resources/hbase-default.xml | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/hbase-common/src/main/resources/hbase-default.xml b/hbase-common/src/main/resources/hbase-default.xml
index e06561cfcd4..680d762ef22 100644
--- a/hbase-common/src/main/resources/hbase-default.xml
+++ b/hbase-common/src/main/resources/hbase-default.xml
@@ -1049,12 +1049,13 @@ possible configurations would overwhelm and obscure the important.
   </property>
   <property>
     <name>hbase.lease.recovery.dfs.timeout</name>
-    <value>61000</value>
+    <value>64000</value>
     <description>
-        How long between dfs recover lease invocations. Should be just larger than how long
-        it takes the namenode to timeout trying to reach a datanode; usually
-        dfs.socket.timeout.  If HBase asked hdfs its cluster configs, we would not need
-        this config.  See the end of HBASE-8389 for more.
+        How long between dfs recover lease invocations. Should be larger than the sum of
+        the time it takes for the namenode to issue a block recovery command as part of
+        datanode; dfs.heartbeat.interval and the time it takes for the primary
+        datanode, performing block recovery to timeout on a dead datanode; usually
+        dfs.socket.timeout. See the end of HBASE-8389 for more.
     </description>
   </property>
 </configuration>