[
https://issues.apache.org/jira/browse/YARN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328375#comment-14328375
]
Li Lu commented on YARN-3033:
-----------------------------
Thanks [~djp]! Some quick comments:
bq. I think we should mention our best-effort to place logical app aggregator
to be on the same physical node with AM containers, given the assumption that
AM could consume aggregator service heavier so we want to keep data transferred
in local as much as possible.
bq. For the reason I mentioned above, we should do our best effort to keep
logical aggregator stay with AM container and we don't have to have different
policies for different cases.
I agree. We should make every effort to improve the locality here. Will cover
this later.
bq. I didn't see the discussion on launching (or we call binding - to physical
aggregator) the logical aggregator (by who and how). I assume this is the scope
of this JIRA. Isn't it?
Yes. Let's focus on launching aggregators for the whole flow in this JIRA. We
may then consider if we need a separate JIRA for the standalone mode.
> [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)
