[
https://issues.apache.org/jira/browse/HADOOP-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307486#comment-14307486
]
Hadoop QA commented on HADOOP-8233:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12520685/HADOOP-8233-branch-0.23.2.patch
against trunk revision fb06c00.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5604//console
This message is automatically generated.
> Turn CRC checking off for 0 byte size and differing blocksizes
> --------------------------------------------------------------
>
> Key: HADOOP-8233
> URL: https://issues.apache.org/jira/browse/HADOOP-8233
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.23.3
> Reporter: Dave Thompson
> Assignee: Dave Thompson
> Attachments: HADOOP-8233-branch-0.23.2.patch
>
>
> DistcpV2 (hadoop-tools/hadoop-distcp/..) can fail from checksum failure,
> sometimes when copying a 0 byte file. Root cause of this may have to do
> with an inconsistent nature of HDFS when creating 0 byte files, however
> distcp can avoid this issue by not checking CRC when size is zero.
> Further, distcp fails checksum when copying from two clusters that use
> different blocksizes. In this case it does not make sense to check CRC, as
> it is a guaranteed failure.
> We need to turn CRC checking off for the above two cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
