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

["Aaron Kimball (JIRA)" <ji...@apache.org>]

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

Aaron Kimball updated MAPREDUCE-1127:
-------------------------------------

    Attachment: MAPREDUCE-1127.patch

Here's a patch that sets the task timeout to the greater of the user-defined timeout or 30 minutes when the destination filesystem is S3.

No automated tests because it's hard to auto-test S3. I ran manual tests as follows:

* start a pseudo-distributed cluster. Put some files in HDFS
* Ran an S3 upload: {{bin/hadoop distcp /user/aaron s3n://$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY@<bucket>/upload}}
** Verified that the files were uploaded correctly
** Looked at the job.xml file on the jobtracker; verified that {{mapreduce.task.timeout}} was set to 1800000.
* Ran an HDFS/HDFS copy: {{bin/hadoop distcp /user/aaron /user/test}}
** Verified that the files were copied correctly.
** Looked at the job.xml file on the jobtracker; verified that {{mapreduce.task.timeout}} was set to 600000 per mapred-default.xml.

> 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.