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
This commit is contained in:
parent
464eb5d12d
commit
ebffc939ea
|
@ -1049,12 +1049,13 @@ possible configurations would overwhelm and obscure the important.
|
||||||
</property>
|
</property>
|
||||||
<property>
|
<property>
|
||||||
<name>hbase.lease.recovery.dfs.timeout</name>
|
<name>hbase.lease.recovery.dfs.timeout</name>
|
||||||
<value>61000</value>
|
<value>64000</value>
|
||||||
<description>
|
<description>
|
||||||
How long between dfs recover lease invocations. Should be just larger than how long
|
How long between dfs recover lease invocations. Should be larger than the sum of
|
||||||
it takes the namenode to timeout trying to reach a datanode; usually
|
the time it takes for the namenode to issue a block recovery command as part of
|
||||||
dfs.socket.timeout. If HBase asked hdfs its cluster configs, we would not need
|
datanode; dfs.heartbeat.interval and the time it takes for the primary
|
||||||
this config. See the end of HBASE-8389 for more.
|
datanode, performing block recovery to timeout on a dead datanode; usually
|
||||||
|
dfs.socket.timeout. See the end of HBASE-8389 for more.
|
||||||
</description>
|
</description>
|
||||||
</property>
|
</property>
|
||||||
</configuration>
|
</configuration>
|
||||||
|
|
Loading…
Reference in New Issue