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

Hadoop QA commented on TEZ-2265:
--------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 4 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 2.0.3) 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.TestAMRecovery

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

This message is automatically generated.

> All inputs/outputs in a task share the same counter object
> ----------------------------------------------------------
>
>                 Key: TEZ-2265
>                 URL: https://issues.apache.org/jira/browse/TEZ-2265
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-2265.1.patch
>
>
> This makes one input which reads the value of a counter to see updates that 
> were made by some other input/output. Any decisions based on those counter 
> values could be wrong and as of today, the output data size reported  in 
> vertex manager event or by shuffle pipelining is potentially wrong.
> Simple fix would be to have each IO have their own counters and merge them 
> before reporting back up in the heartbeat.



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

Reply via email to