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

TezQA commented on TEZ-3440:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12831604/TEZ-3440-v1.patch
  against master revision ad1fb62.

    {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:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> Shuffling to memory can get out-of-sync when fetching multiple compressed map 
> outputs
> -------------------------------------------------------------------------------------
>
>                 Key: TEZ-3440
>                 URL: https://issues.apache.org/jira/browse/TEZ-3440
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Nathan Roberts
>            Assignee: Nathan Roberts
>         Attachments: TEZ-3440-v1.patch, TEZ-3440.patch
>
>
> Haven't verified yet but certainly looks like tez needs same fix as 
> MAPREDUCE-5308 in IFile.
> Specifically saw this because downstream tasks were reporting enough fetch 
> failures that long-running upstream tasks had to be re-run, which makes job 
> run for much longer than it needs.
> Usually shows itself as an "Invalid map id" error on a multi-map fetch on 
> part 2-n (i.e. never the first one).
>  



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

Reply via email to