[ 
https://issues.apache.org/jira/browse/HADOOP-18723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717127#comment-17717127
 ] 

ASF GitHub Bot commented on HADOOP-18723:
-----------------------------------------

symious opened a new pull request, #5603:
URL: https://github.com/apache/hadoop/pull/5603

   ### Description of PR
   
   We encountered some errors of mismatch checksum during Distcp jobs. It took 
us some time to figure out that checksum type is different.
   
   Adding error logs shall help us to figure out such problems faster.
   
   ### How was this patch tested?
   
   Add unit test.
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> Add detail logs if distcp checksum mismatch
> -------------------------------------------
>
>                 Key: HADOOP-18723
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18723
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>
> We encountered some errors of mismatch checksum during Distcp jobs. It took 
> us some time to figure out that checksum type is different.
> Adding error logs shall help us to figure out such problems faster.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to