You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2008/12/01 20:43:44 UTC
[jira] Commented: (HADOOP-4732) connectionTimeout and readTimeout
are passed in wrong order in ReduceTask.java
[ https://issues.apache.org/jira/browse/HADOOP-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652122#action_12652122 ]
Hudson commented on HADOOP-4732:
--------------------------------
Integrated in Hadoop-trunk #675 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/675/])
. Pass connection and read timeouts in the correct order when
setting up fetch in reduce. Contributed by Amareshwari Sriramadasu.
> connectionTimeout and readTimeout are passed in wrong order in ReduceTask.java
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4732
> URL: https://issues.apache.org/jira/browse/HADOOP-4732
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: patch-4732.txt
>
>
> In ReduceTask.java, The parameters for method calls for getInputStream(URLConnection connection, int connectionTimeout, int readTimeout) should be in that order. Now it is
> {code}
> InputStream input = getInputStream(connection, DEFAULT_READ_TIMEOUT,
> STALLED_COPY_TIMEOUT);
> {code}
> It works now because both DEFAULT_READ_TIMEOUT and STALLED_COPY_TIMEOUT have the same value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.