You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/05/04 19:53:13 UTC

[jira] [Updated] (TEZ-2325) Route status update event directly to the attempt

     [ https://issues.apache.org/jira/browse/TEZ-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated TEZ-2325:
-----------------------------
    Priority: Critical  (was: Major)

> 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
>            Priority: Critical
>             Fix For: 0.7.0
>
>         Attachments: TEZ-2325.1.patch, TEZ-2325.2.patch, TEZ-2325.3.patch, TEZ-2325.4.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)