Zhijie Shen commented on YARN-3116:

[~kkaranasos], thanks for notifying us of YARN-2882. I took a quick look at the 
jira. Our approach seems to be similar, but it seems that we're on parallel 
tracks. While YARN-2882 defines two container type for container related API so 
as to differ the container request to RM or NM, what we want to label a 
container here aims to let NM know if the container hosts AM or not. This is 
completely internal information, and users are blind to this type and also not 
able to set/change it. And this is why we propose to pass this information via 
ContainerTokenIndentifier instead of ContainerLaunchContext. Thoughts?

> [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

Reply via email to