You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2013/06/27 19:22:35 UTC

svn commit: r1497464 - /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml

Author: stack
Date: Thu Jun 27 17:22:35 2013
New Revision: 1497464

URL: http://svn.apache.org/r1497464
Log:
HBASE-8813 Fix time b/w recoverLease invocations from HBASE 8449

Modified:
    hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml

Modified: hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml
URL: http://svn.apache.org/viewvc/hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml?rev=1497464&r1=1497463&r2=1497464&view=diff
==============================================================================
--- hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml (original)
+++ hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml Thu Jun 27 17:22:35 2013
@@ -1049,12 +1049,13 @@ possible configurations would overwhelm 
   </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>