[jira] [Commented] (TEZ-3237) Corrupted shuffle transfers to disk are not detected during transfer

["TezQA (JIRA)" <ji...@apache.org>]

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

TezQA commented on TEZ-3237:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12803492/TEZ-3237.001.patch
  against master revision 88bd5b9.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The following test timeouts occurred in :
 org.apache.tez.test.TestSecureShuffle

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/1715//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1715//console

This message is automatically generated.

> Corrupted shuffle transfers to disk are not detected during transfer
> --------------------------------------------------------------------
>
>                 Key: TEZ-3237
>                 URL: https://issues.apache.org/jira/browse/TEZ-3237
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>         Attachments: TEZ-3237.001.patch
>
>
> When a shuffle transfer is larger than the single transfer limit it gets written straight to disk during the transfer.  Unfortunately there are no checksum validations performed during that transfer, so if the data is corrupted at the source or during transmit it goes undetected.  Only later when the task tries to consume the transferred data is the error detected, but at that point it's too late to blame the source task for the error.



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