You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/04/03 17:24:13 UTC
[jira] Commented: (HADOOP-5464) DFSClient does not treat write
timeout of 0 properly
[ https://issues.apache.org/jira/browse/HADOOP-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695420#action_12695420 ]
Hudson commented on HADOOP-5464:
--------------------------------
Integrated in Hadoop-trunk #796 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/796/])
> 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
> Fix For: 0.21.0
>
> Attachments: HADOOP-5464.patch
>
>
> {{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.