[
https://issues.apache.org/jira/browse/YARN-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307194#comment-14307194
]
Naganarasimha G R commented on YARN-3034:
-----------------------------------------
Modifications as part of the patch :
1) Created RMTimelineAggregator by extending BaseAggregatorService (and the
required dependencies)
2) Refactored SystemMetricsPubliser and moved the event handling part to
RMTimelineAggregator itself
3) Removed publishing of Container related life cycle events from RM.
4) Refactored the test cases to remove testcases for storing container related
life cycle events.
Pending
1) Once ATS reader interface and Dataobjects are finalized, can further stub
and complete TestSystemMetricsPublisher
some points which required further discussion
1) 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 ?
2) AppAttempt needs to be Entity or event of ApplicationEntity ? i feel later
option is better
3) It would better for BaseAggregatorService.postEntities & postEntitiesAsync
to throw YARNException and IOException as part of method signature.
> 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)
