[
https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329671#comment-14329671
]
Li Lu commented on YARN-3033:
-----------------------------
Hi [~sjlee0], thanks for the comments! I thing I used the wrong name
"Application Level Aggregator inside RM" here. I think a more appropriate name
would be "aggregator inside RM for app data". I agree that we should strictly
limit the total number of this type of aggregators (one per RM seems to be
reasonable for now). We may want to reuse the implementation for web
server/data storage layer in aggregator collection for this aggregator as well,
by simply wrap it to an aggregator collection?
For the second point, yes, we can (and should always) reuse the same hbase
client for all app level aggregators on the same node.
> [Aggregator wireup] Implement NM starting the ATS writer companion
> ------------------------------------------------------------------
>
> Key: YARN-3033
> URL: https://issues.apache.org/jira/browse/YARN-3033
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Sangjin Lee
> Assignee: Li Lu
> Attachments: MappingandlaunchingApplevelTimelineaggregators.pdf
>
>
> Per design in YARN-2928, implement node managers starting the ATS writer
> companion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
