[
https://issues.apache.org/jira/browse/TEZ-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523641#comment-14523641
]
Bikas Saha commented on TEZ-1897:
---------------------------------
>From what I see - AbstractService#start()->serviceStart()->end up calling
>AsyncDispatcher->serviceStart() since it overrides
>CompositeService#serviceStart(). So the derived class must call its parents
>serviceStart(). MRAppMaster is also written that way.
Thanks! We can remove this draining code and other unused code when we remove
AsyncDispatcher.
> Create a concurrent version of AsyncDispatcher
> ----------------------------------------------
>
> Key: TEZ-1897
> URL: https://issues.apache.org/jira/browse/TEZ-1897
> Project: Apache Tez
> Issue Type: Task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1897.1.patch, TEZ-1897.2.patch, TEZ-1897.3.patch,
> TEZ-1897.4.patch, TEZ-1897.5.patch, TEZ-1897.6.patch, TEZ-1897.7.patch
>
>
> Currently, it processes events on a single thread. For events that can be
> executed in parallel, e.g. vertex manager events, allowing higher concurrency
> may be beneficial.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
