[
https://issues.apache.org/jira/browse/YARN-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314763#comment-14314763
]
Sangjin Lee commented on YARN-3034:
-----------------------------------
Thanks [~Naganarasimha]! I'll go over the patch today...
bq. Whether we require Multithreaded Dispatcher as we are not publishing
container life cycle events and if normal dispatcher is ok whether to use
rmcontext.getDispatcher ?
For publishing app lifecycle events only, I suspect a normal dispatcher might
be OK. However, there could be more use cases in the future. If it is not too
complicated, using a multi-threaded dispatcher might be bit preferable IMO.
Thoughts?
bq. AppAttempt needs to be Entity or event of ApplicationEntity ? i feel later
option is better
How is it today with the current ATS? If the same container can be part of
different app attempts (e.g. successive AMs managing the same set of
containers), then app attempts can't be separate entities? [~zjshen]?
> implement RM starting its ATS writer
> ------------------------------------
>
> Key: YARN-3034
> URL: https://issues.apache.org/jira/browse/YARN-3034
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Naganarasimha G R
> Attachments: YARN-3034.20150205-1.patch
>
>
> Per design in YARN-2928, implement resource managers starting their own ATS
> writers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
