[
https://issues.apache.org/jira/browse/MAPREDUCE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767590#action_12767590
]
Doug Cutting commented on MAPREDUCE-972:
----------------------------------------
> However, for this issue, patching either the old or new API is a non-starter.
+1 We should not change the FileSystem API in this issue.
There appear to be both short and long-term fixes for this issue. The
shortest-term is just to bump up the timeout for S3 distcp jobs. The longest
is adding FileSystem support for long renames.
Questions:
- Will such a short-term fix suffice until the long-term can be addressed
(0.22, probably)? If so, then there's perhaps no in point considering a more
complex interim solution.
- Should we associate this Jira issue with the short or long-term fix? If
long, then we might make it depend on a FileSystem API change, to support
progress callbacks.
> distcp can timeout during rename operation to s3
> ------------------------------------------------
>
> Key: MAPREDUCE-972
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-972
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distcp
> Affects Versions: 0.20.1
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-972.2.patch, MAPREDUCE-972.3.patch,
> MAPREDUCE-972.4.patch, MAPREDUCE-972.5.patch, MAPREDUCE-972.patch
>
>
> rename() in S3 is implemented as copy + delete. The S3 copy operation can
> perform very slowly, which may cause task timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
