You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/04 01:00:55 UTC
[jira] [Updated] (HDFS-4807)
DFSOutputStream.createSocketForPipeline() should not include timeout
extension on connect
[ https://issues.apache.org/jira/browse/HDFS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HDFS-4807:
-----------------------------------
Fix Version/s: (was: 3.0.0)
> 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.1.0-beta, 0.23.8
> Reporter: Kihwal Lee
> Assignee: Cristina L. Abad
> Fix For: 2.1.0-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 was sent by Atlassian JIRA
(v6.3.4#6332)