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 "Ayush Saxena (JIRA)" <ji...@apache.org> on 2019/07/20 08:29:00 UTC
[jira] [Updated] (HADOOP-16440) Distcp can not preserve timestamp
with -delete option
[ https://issues.apache.org/jira/browse/HADOOP-16440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ayush Saxena updated HADOOP-16440:
----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.1.3
3.2.1
3.3.0
Status: Resolved (was: Patch Available)
> Distcp can not preserve timestamp with -delete option
> ------------------------------------------------------
>
> Key: HADOOP-16440
> URL: https://issues.apache.org/jira/browse/HADOOP-16440
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.7.7, 3.1.2
> Reporter: ludun
> Assignee: ludun
> Priority: Major
> Fix For: 3.3.0, 3.2.1, 3.1.3
>
> Attachments: HDFS-14261.001.patch, HDFS-14621.002.patch, HDFS-14621.003.patch, HDFS-14621.004.patch
>
>
> Use distcp with -prbugpcaxt and -delete to copy data between cluster.
> hadoop distcp -Dmapreduce.job.queuename="QueueA" -prbugpcaxt -update -delete hdfs://sourcecluster/user/hive/warehouse/sum.db hdfs://destcluster/user/hive/warehouse/sum.db
> After distcp, we found the timestamp of dest is different from source, and the timestamp of some directory was the time distcp running.
> Check the code of distcp, in CopyCommitter, it preserves time first then process -delete option which will change the timestamp of dest directory. So we should process -delete option first.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org