[
https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621089#comment-14621089
]
Giovanni Matteo Fumarola commented on YARN-3116:
------------------------------------------------
[~kkaranasos], thanks for the observation. As [~zjshen] rightly pointed out,
YARN-2882 and YARN-3116 are complementary. We are adding the container type
enum to notify the NM whether its an AM container or not. This is purely
internal and we deliberately don't want to expose it to the Application for
security reasons while in YARN-2882, you want to expose the container type to
the application.
> [Collector wireup] We need an assured way to determine if a container is an
> AM container on NM
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-3116
> URL: https://issues.apache.org/jira/browse/YARN-3116
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, timelineserver
> Reporter: Zhijie Shen
> Assignee: Giovanni Matteo Fumarola
> Attachments: YARN-3116.patch, YARN-3116.v2.patch, YARN-3116.v3.patch,
> YARN-3116.v4.patch, YARN-3116.v5.patch, YARN-3116.v6.patch,
> YARN-3116.v7.patch, YARN-3116.v8.patch
>
>
> In YARN-3030, to start the per-app aggregator only for a started AM
> container, we need to determine if the container is an AM container or not
> from the context in NM (we can do it on RM). This information is missing,
> such that we worked around to considered the container with ID "xxxx_01" as
> the AM container. Unfortunately, this is neither necessary or sufficient
> condition. We need to have a way to determine if a container is an AM
> container on NM. We can add flag to the container object or create an API to
> do the judgement. Perhaps the distributed AM information may also be useful
> to YARN-2877.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
