hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4807) DFSOutputStream.createSocketForPipeline() should not include timeout extension on connect
Date Thu, 23 May 2013 21:47:21 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665719#comment-13665719
] 

Hudson commented on HDFS-4807:
------------------------------

Integrated in Hadoop-trunk-Commit #3784 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3784/])
    HDFS-4807. createSocketForPipeline() should not include timeout extension on connect.
Contributed by Cristina Abad. (Revision 1485861)

     Result = SUCCESS
kihwal : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1485861
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSOutputStream.java

                
> DFSOutputStream.createSocketForPipeline() should not include timeout extension on connect
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-4807
>                 URL: https://issues.apache.org/jira/browse/HDFS-4807
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 2.0.5-beta, 0.23.8
>            Reporter: Kihwal Lee
>            Assignee: Cristina L. Abad
>             Fix For: 3.0.0, 2.0.5-beta, 0.23.8
>
>         Attachments: 4807.branch-0.23.patch, 4807.branch-0.23.v2.patch, 4807.branch-2.patch,
4807.branch-2.v2.patch, 4807.trunk.patch, 4807.trunk.v2.patch
>
>
> In createSocketForPipeline(), connect() is called with a timeout set to (socket_timeout
+ read_extension * num_datanodes). Since it is simply connecting to a single node, it does
not make sense to increase connection timeout based on the number of datanodes.
> DFSInputStream is doing it correctly both in trunk and branch-2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message