Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 5 May 2016 06:49:12 +0000 (UTC)
From: "Lin Yiqun (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12963205.1461776543000.116062.1462430952956@Atlassian.JIRA>
In-Reply-To: <JIRA.12963205.1461776543000@Atlassian.JIRA>
References: <JIRA.12963205.1461776543000@Atlassian.JIRA> <JIRA.12963205.1461776543885@arcas>
Subject: [jira] [Updated] (HADOOP-13091) DistCp masks potential CRC check
 failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 05 May 2016 06:49:15 -0000


     [ https://issues.apache.org/jira/browse/HADOOP-13091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lin Yiqun updated HADOOP-13091:
-------------------------------
    Attachment: HADOOP-13091.003.patch

> DistCp masks potential CRC check failures
> -----------------------------------------
>
>                 Key: HADOOP-13091
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13091
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Elliot West
>            Assignee: Lin Yiqun
>         Attachments: HADOOP-13091.003.patch, HDFS-10338.001.patch, HDFS-10338.002.patch
>
>
> There appear to be edge cases whereby CRC checks may be circumvented when requests for checksums from the source or target file system fail. In this event CRCs could differ between the source and target and yet the DistCp copy would succeed, even when the 'skip CRC check' option is not being used.
> The code in question is contained in the method [{{org.apache.hadoop.tools.util.DistCpUtils#checksumsAreEqual(...)}}|https://github.com/apache/hadoop/blob/release-2.7.1/hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/util/DistCpUtils.java#L457]
> Specifically this code block suggests that if there is a failure when trying to read the source or target checksum then the method will return {{true}} (i.e.  the checksums are equal), implying that the check succeeded. In actual fact we just failed to obtain the checksum and could not perform the check.
> {code}
> try {
>   sourceChecksum = sourceChecksum != null ? sourceChecksum : 
>     sourceFS.getFileChecksum(source);
>   targetChecksum = targetFS.getFileChecksum(target);
> } catch (IOException e) {
>   LOG.error("Unable to retrieve checksum for " + source + " or "
>     + target, e);
> }
> return (sourceChecksum == null || targetChecksum == null ||
>   sourceChecksum.equals(targetChecksum));
> {code}
> I believe that at the very least the caught {{IOException}} should be re-thrown. If this is not deemed desirable then I believe an option ({{--strictCrc}}?) should be added to enforce a strict check where we require that both the source and target CRCs are retrieved, are not null, and are then compared for equality. If for any reason either of the CRCs retrievals fail then an exception is thrown.
> Clearly some {{FileSystems}} do not support CRCs and invocations to {{FileSystem.getFileChecksum(...)}} return {{null}} in these instances. I would suggest that these should fail a strict CRC check to prevent users developing a false sense of security in their copy pipeline.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org