[ https://issues.apache.org/jira/browse/TEZ-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509941#comment-14509941 ]
TezQA commented on TEZ-2325: ---------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12727718/TEZ-2325.2.patch against master revision ec7b481. {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 2.0.3) 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/524//testReport/ Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/524//console This message is automatically generated. > Route status update event directly to the attempt > -------------------------------------------------- > > Key: TEZ-2325 > URL: https://issues.apache.org/jira/browse/TEZ-2325 > Project: Apache Tez > Issue Type: Bug > Reporter: Bikas Saha > Assignee: Prakash Ramachandran > Attachments: TEZ-2325.1.patch, TEZ-2325.2.patch > > > Today, all events from the attempt heartbeat are routed to the vertex. then > the vertex routes (if any) status update events to the attempt. This is > unnecessary and potentially creates out of order scenarios. We could route > the status update events directly to attempts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)