hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5464) DFSClient does not treat write timeout of 0 properly
Date Tue, 31 Mar 2009 19:40:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raghu Angadi updated HADOOP-5464:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I just committed this.

> 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.


Mime
View raw message