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 "Steve Loughran (Jira)" <ji...@apache.org> on 2020/07/29 13:36:00 UTC
[jira] [Commented] (MAPREDUCE-7287) Distcp will delete exists file
, If we use "--delete and --update" options and distcp file.
[ https://issues.apache.org/jira/browse/MAPREDUCE-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167215#comment-17167215 ]
Steve Loughran commented on MAPREDUCE-7287:
-------------------------------------------
sounds like a regression to me. That change went in to deal with delete throttling, and yes, was biased towards directories
Do you want to have a go at fixing it?
> Distcp will delete exists file , If we use "--delete and --update" options and distcp file.
> --------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-7287
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7287
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distcp
> Affects Versions: 3.2.1
> Reporter: zhengchenyu
> Priority: Major
> Fix For: 3.3.1
>
>
> hdfs://ns1/tmp/a is an existing file, hdfs://ns2/tmp/a is also an existing file.
> When I run this command,
> {code}
> hadoop distcp -delete -update hdfs://ns1/tmp/a hdfs://ns2/tmp/a
> {code}
> I Found hdfs://ns2/tmp/a is deleted unpectectedly.
>
> Then problem is DeletedDirTracker. Because here we only distcp a file (not a directory), the varialbe `directories` in DeletedDirTracker is not set.
> Maybe I think DeletedDirTracker only consider directory in design stage. But we distcp only a file, they are deleted unpectectedly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org