[
https://issues.apache.org/jira/browse/HDFS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cristina L. Abad updated HDFS-4807:
-----------------------------------
Status: Patch Available (was: Open)
The new (v2) patches use the correct timeout after making the connection.
> 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
> 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
