You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Brandon Li (JIRA)" <ji...@apache.org> on 2012/05/25 22:19:23 UTC

[jira] [Updated] (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:all-tabpanel ]

Brandon Li updated HADOOP-5464:
-------------------------------

    Attachment: HADOOP-5464.branch1.patch

Backport the fix to branch 1.1

                
> DFSClient does not treat write timeout of 0 properly
> ----------------------------------------------------
>
>                 Key: HADOOP-5464
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5464
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.17.0
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5464.branch1.patch, 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira