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

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2015/05/12 23:46:00 UTC

[jira] [Resolved] (TEZ-93) Use central AsyncDispatcher to relay events. Process events on different events based threads.

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

Bikas Saha resolved TEZ-93.
---------------------------
    Resolution: Fixed

New dispatchers have been added and conditionally used to route events independently. The infra work for this is done. Any events that need to be offloaded to their own dispatcher can be done with per event jiras.

> Use central AsyncDispatcher to relay events. Process events on different events based threads.
> ----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-93
>                 URL: https://issues.apache.org/jira/browse/TEZ-93
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Bikas Saha
>              Labels: TEZ-1
>
> Currently the central dispatcher is a central lock and concurrent work gets bottlenecked on it. This can slow down the AM. If each event type was handled in its own thread then different event types could proceed in parallel. This would maintain serialization of events within an event type and may be overridden by the specific event handlers to make even them concurrent.



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