big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HDFS-12920. HDFS default value change (with adding time unit) breaks old version MR tarball work with new version (3.0) of hadoop. (#3227)

Browse Source 
Revert "HDFS-10845. Change defaults in hdfs-site.xml to match timeunit type. Contributed by Yiqun Lin"

This reverts commit b6d839a60c.

 Conflicts:
	hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml

(cherry picked from commit 2f2f822488)
This commit is contained in:
Akira Ajisaka 2021-07-26 01:53:39 +09:00
parent e89d30b6b7
commit 3f573b6751
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
View File

@ -789,7 +789,7 @@
<property>
<name>dfs.blockreport.initialDelay</name>
<value>0s</value>
<value>0</value>
<description>
Delay for first block report in seconds. Support multiple time unit
suffix(case insensitive), as described in dfs.heartbeat.interval.If
@ -834,7 +834,7 @@
<property>
<name>dfs.datanode.directoryscan.interval</name>
<value>21600s</value>
<value>21600</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
@ -873,7 +873,7 @@
<property>
<name>dfs.heartbeat.interval</name>
<value>3s</value>
<value>3</value>
<description>
Determines datanode heartbeat interval in seconds.
Can use the following suffix (case insensitive):
@ -1086,7 +1086,7 @@
<property>
<name>dfs.namenode.decommission.interval</name>
<value>30s</value>
<value>30</value>
<description>Namenode periodicity in seconds to check if
decommission or maintenance is complete. Support multiple time unit
suffix(case insensitive), as described in dfs.heartbeat.interval.
@ -1154,7 +1154,7 @@
<property>
<name>dfs.namenode.redundancy.interval.seconds</name>
<value>3s</value>
<value>3</value>
<description>The periodicity in seconds with which the namenode computes
low redundancy work for datanodes. Support multiple time unit suffix(case insensitive),
as described in dfs.heartbeat.interval.
@ -1270,7 +1270,7 @@
<property>
<name>dfs.namenode.checkpoint.period</name>
<value>3600s</value>
<value>3600</value>
<description>
The number of seconds between two periodic checkpoints.
Support multiple time unit suffix(case insensitive), as described
@ -1290,7 +1290,7 @@
<property>
<name>dfs.namenode.checkpoint.check.period</name>
<value>60s</value>
<value>60</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),
@ -1747,7 +1747,7 @@
<property>
<name>dfs.client.datanode-restart.timeout</name>
<value>30s</value>
<value>30</value>
<description>
Expert only. The time to wait, in seconds, from reception of an
datanode shutdown notification for quick restart, until declaring
@ -1817,7 +1817,7 @@
<property>
<name>dfs.ha.log-roll.period</name>
<value>120s</value>
<value>120</value>
<description>
How often, in seconds, the StandbyNode should ask the active to
roll edit logs. Since the StandbyNode only reads from finalized
@ -1832,7 +1832,7 @@
<property>
<name>dfs.ha.tail-edits.period</name>
<value>60s</value>
<value>60</value>
<description>
How often, the StandbyNode and ObserverNode should check if there are new
edit log entries ready to be consumed. This is the minimum period between
@ -3749,7 +3749,7 @@
<property>
<name>dfs.datanode.bp-ready.timeout</name>
<value>20s</value>
<value>20</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