[
https://issues.apache.org/jira/browse/HADOOP-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681014#action_12681014
]
Raghu Angadi commented on HADOOP-5464:
--------------------------------------
A work around is to use a very large value instead of 0.
> DFSClient does not treat write timeout of 0 properly
> ----------------------------------------------------
>
> Key: HADOOP-5464
> URL: https://issues.apache.org/jira/browse/HADOOP-5464
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
>
> {{dfs.datanode.socket.write.timeout}} is used for sockets to and from
> datanodes. It is 8 minutes by default. Some users set this to 0, effectively
> disabling the write timeout (for some specific reasons).
> When this is set to 0, DFSClient sets the timeout to 5 seconds by mistake
> while writing to DataNodes. This is exactly the opposite of real intention of
> setting it to 0 since 5 seconds is too short.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
