|
@@ -650,7 +650,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.blockreport.initialDelay</name>
|
|
|
- <value>0</value>
|
|
|
+ <value>0s</value>
|
|
|
<description>
|
|
|
Delay for first block report in seconds. Support multiple time unit
|
|
|
suffix(case insensitive), as described in dfs.heartbeat.interval.
|
|
@@ -694,7 +694,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.datanode.directoryscan.interval</name>
|
|
|
- <value>21600</value>
|
|
|
+ <value>21600s</value>
|
|
|
<description>Interval in seconds for Datanode to scan data directories and
|
|
|
reconcile the difference between blocks in memory and on the disk.
|
|
|
Support multiple time unit suffix(case insensitive), as described
|
|
@@ -732,7 +732,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.heartbeat.interval</name>
|
|
|
- <value>3</value>
|
|
|
+ <value>3s</value>
|
|
|
<description>
|
|
|
Determines datanode heartbeat interval in seconds.
|
|
|
Can use the following suffix (case insensitive):
|
|
@@ -942,7 +942,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.namenode.decommission.interval</name>
|
|
|
- <value>30</value>
|
|
|
+ <value>30s</value>
|
|
|
<description>Namenode periodicity in seconds to check if decommission is
|
|
|
complete. Support multiple time unit suffix(case insensitive), as described
|
|
|
in dfs.heartbeat.interval.
|
|
@@ -973,7 +973,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.namenode.replication.interval</name>
|
|
|
- <value>3</value>
|
|
|
+ <value>3s</value>
|
|
|
<description>The periodicity in seconds with which the namenode computes
|
|
|
replication work for datanodes. Support multiple time unit suffix(case insensitive),
|
|
|
as described in dfs.heartbeat.interval.
|
|
@@ -1071,7 +1071,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.namenode.checkpoint.period</name>
|
|
|
- <value>3600</value>
|
|
|
+ <value>3600s</value>
|
|
|
<description>
|
|
|
The number of seconds between two periodic checkpoints.
|
|
|
Support multiple time unit suffix(case insensitive), as described
|
|
@@ -1090,7 +1090,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.namenode.checkpoint.check.period</name>
|
|
|
- <value>60</value>
|
|
|
+ <value>60s</value>
|
|
|
<description>The SecondaryNameNode and CheckpointNode will poll the NameNode
|
|
|
every 'dfs.namenode.checkpoint.check.period' seconds to query the number
|
|
|
of uncheckpointed transactions. Support multiple time unit suffix(case insensitive),
|
|
@@ -1433,7 +1433,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.client.datanode-restart.timeout</name>
|
|
|
- <value>30</value>
|
|
|
+ <value>30s</value>
|
|
|
<description>
|
|
|
Expert only. The time to wait, in seconds, from reception of an
|
|
|
datanode shutdown notification for quick restart, until declaring
|
|
@@ -1502,7 +1502,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.ha.log-roll.period</name>
|
|
|
- <value>120</value>
|
|
|
+ <value>120s</value>
|
|
|
<description>
|
|
|
How often, in seconds, the StandbyNode should ask the active to
|
|
|
roll edit logs. Since the StandbyNode only reads from finalized
|
|
@@ -1516,7 +1516,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.ha.tail-edits.period</name>
|
|
|
- <value>60</value>
|
|
|
+ <value>60s</value>
|
|
|
<description>
|
|
|
How often, in seconds, the StandbyNode should check for new
|
|
|
finalized log segments in the shared edits log.
|
|
@@ -2950,7 +2950,7 @@
|
|
|
|
|
|
<property>
|
|
|
<name>dfs.datanode.bp-ready.timeout</name>
|
|
|
- <value>20</value>
|
|
|
+ <value>20s</value>
|
|
|
<description>
|
|
|
The maximum wait time for datanode to be ready before failing the
|
|
|
received request. Setting this to 0 fails requests right away if the
|