[
https://issues.apache.org/jira/browse/MAPREDUCE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767919#action_12767919
]
Chris Douglas commented on MAPREDUCE-1127:
------------------------------------------
A task timeout of 0, IIRC, means that the task should never time out. It should
be considered "larger" than {{MIN_S3_TASK_TIMEOUT}}.
Special-casing S3 in distcp is not ideal, but it's a passable workaround until
HADOOP-6324 is addressed or S3's rename stops sucking.
> distcp should timeout later during S3-based transfers
> -----------------------------------------------------
>
> Key: MAPREDUCE-1127
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1127
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: distcp
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1127.patch
>
>
> Per MAPREDUCE-972, rename and other operations on distcp can take longer than
> the typical mapreduce task timeout. As an interim fix, this timeout should be
> increased when the distcp destination is S3.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
