You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2020/03/13 18:57:00 UTC
[jira] [Commented] (HADOOP-16776) backport HADOOP-16775: distcp
copies to s3 are randomly corrupted
[ https://issues.apache.org/jira/browse/HADOOP-16776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059015#comment-17059015 ]
Steve Loughran commented on HADOOP-16776:
-----------------------------------------
bq. I'm appalled and dismayed. You're blocking fixes for a critical data corruption bug due to a personal interest in advancing branch-3? We've been telling customers for months that it was impossible for distcp to copy the wrong data and they must be overwriting the s3 destination.
sorry, I'd missed this.
Sorry, I'd thought we had backported the -direct option everywhere, which is why I didn't think it was so important.
If we don't have -direct in a release, yes, we should eliminate this. So I'm going to re-open and we can get it into branch-2, even if not the 2.8 release,
> backport HADOOP-16775: distcp copies to s3 are randomly corrupted
> -----------------------------------------------------------------
>
> Key: HADOOP-16776
> URL: https://issues.apache.org/jira/browse/HADOOP-16776
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
> Affects Versions: 2.8.0, 3.0.0, 2.10.0
> Reporter: Amir Shenavandeh
> Priority: Blocker
> Labels: DistCp
> Attachments: HADOOP-16776-branch-2.8-001.patch, HADOOP-16776-branch-2.8-002.patch
>
>
> This is to back port HADOOP-16775 to hadoop 2.8 branch.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org