[
https://issues.apache.org/jira/browse/HADOOP-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070531#comment-17070531
]
Ayush Saxena commented on HADOOP-16946:
---------------------------------------
should be ok then.
The only doubt I am having is, whether the log was not trying to depict the
case of overwrite?
That the src file of size x overwrote dst file of size y? So as to keep the
record of the file deleted due to overwrite?
but I am not sure and even couldn't dig into it, so nothing blocking from my
side...
> Distcp print wrong log info when use -log
> -----------------------------------------
>
> Key: HADOOP-16946
> URL: https://issues.apache.org/jira/browse/HADOOP-16946
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 3.1.1
> Reporter: liuyanyu
> Assignee: liuyanyu
> Priority: Minor
> Attachments: HDFS-15241.001.patch, image-2020-03-25-17-28-33-394.png
>
>
> when run distcp with -log /logpath -v, distcp will print copy status and file
> info to /logpath, but print log with wrong file zise. The logs print as
> follows:
> FILE_COPIED: source=hdfs://ns1/test/stax2-api-3.1.4.jar, size=161867 -->
> target=hdfs://ns1/tmp/target/stax2-api-3.1.4.jar, size=0
> As I analysis ,the root cause is as follows:
> targrtFileStatus got before copying. So targrtFileStatus is null. Here should
> get targrtFileStatus again after file copying.
> !image-2020-03-25-17-28-33-394.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
