[
https://issues.apache.org/jira/browse/HADOOP-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071742#comment-17071742
]
Hadoop QA commented on HADOOP-16946:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 8s{color}
| {color:red} HADOOP-16946 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-16946 |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/16807/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> 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,
> image-2020-03-31-20-36-28-759.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]
