You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2009/11/05 01:41:35 UTC

[jira] Updated: (MAPREDUCE-1127) distcp should timeout later during S3-based transfers

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated MAPREDUCE-1127:
-------------------------------------

    Status: Open  (was: Patch Available)

On reflection... the documentation change is in 0.21, so it may not be worth adding and removing this special case in 0.22. Would you object to calling the documentation change "sufficient" and exploring real fixes for S3 in 0.22? Depending on how that is resolved, this workaround may become necessary again.

> 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.2.patch, 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.