HDFS-13719. Docs around dfs.image.transfer.timeout are misleading. Contributed by Kitti Nansi.

This commit is contained in:
Andrew Wang 2018-07-09 15:17:26 +02:00
parent 512d20e9c5
commit 913417bbea
1 changed files with 5 additions and 8 deletions

View File

@ -1235,11 +1235,10 @@
<name>dfs.image.transfer.timeout</name> <name>dfs.image.transfer.timeout</name>
<value>60000</value> <value>60000</value>
<description> <description>
Socket timeout for image transfer in milliseconds. This timeout and the related Socket timeout for the HttpURLConnection instance used in the image
dfs.image.transfer.bandwidthPerSec parameter should be configured such transfer. This is measured in milliseconds.
that normal image transfer can complete successfully. This timeout prevents client hangs if the connection is idle
This timeout prevents client hangs when the sender fails during for this configured timeout, during image transfer.
image transfer. This is socket timeout during image transfer.
</description> </description>
</property> </property>
@ -1250,9 +1249,7 @@
Maximum bandwidth used for regular image transfers (instead of Maximum bandwidth used for regular image transfers (instead of
bootstrapping the standby namenode), in bytes per second. bootstrapping the standby namenode), in bytes per second.
This can help keep normal namenode operations responsive during This can help keep normal namenode operations responsive during
checkpointing. The maximum bandwidth and timeout in checkpointing.
dfs.image.transfer.timeout should be set such that normal image
transfers can complete successfully.
A default value of 0 indicates that throttling is disabled. A default value of 0 indicates that throttling is disabled.
The maximum bandwidth used for bootstrapping standby namenode is The maximum bandwidth used for bootstrapping standby namenode is
configured with dfs.image.transfer-bootstrap-standby.bandwidthPerSec. configured with dfs.image.transfer-bootstrap-standby.bandwidthPerSec.