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

TezQA commented on TEZ-3912:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12930547/TEZ-3912.002.patch
  against master revision 3baab55.

    {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 patch failed these unit tests in :
                   
org.apache.tez.runtime.library.common.writers.TestUnorderedPartitionedKVWriter

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

This message is automatically generated.


> Fetchers should be more robust to corrupted inputs
> --------------------------------------------------
>
>                 Key: TEZ-3912
>                 URL: https://issues.apache.org/jira/browse/TEZ-3912
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jason Lowe
>            Assignee: Kuhu Shukla
>            Priority: Major
>         Attachments: TEZ-3912.001.patch, TEZ-3912.002.patch
>
>
> I recently saw a case where a bad node in the cluster produced corrupted 
> shuffle data that caused the codec to throw IllegalArgumentException when 
> trying to fetch.  Fetchers currently only handle IOException and 
> InternalError, and any other type of exception will cause the entire task to 
> be torn down.  We should consider catching Exception like MapReduce does to 
> be more robust in light of other types of errors coming from the codec and 
> allow retries to occur.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to