[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14622756#comment-14622756 ]
Subru Krishnan commented on YARN-3116: -------------------------------------- [~zjshen], I am working with [~kishorch] on YARN-2884 and we do *not* want to expose the _containerType_ to user. We are updating the YARN-2884 patch to use _containerInitializationContext_ to determine if the container is AM or not. Seperately [~kkaranasos] is working on YARN-2882 where he needs to expose the container*Request*Type to the user. That is complementary work & should *not* affect this patch. So can we get this committed soon as YARN-2884 is blocked on this. Thanks! > [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, YARN-3116.v9.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)