[ 
https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606252#comment-14606252
 ] 

Subru Krishnan commented on YARN-3116:
--------------------------------------

Thanks [~zjshen] for the offline discussion with [~giovanni.fumarola]. The 
conclusion was that:
   * we will add a flag in _ContainerTokenIdentifier_ to indicate whether its 
an AM container or not
   * we'll set the flag in 
_SchedulerApplicationAttempt::pullNewlyAllocatedContainersAndNMTokens_ where 
the _ContainerTokenIdentifier_ is created based on whether the current 
container has a master container. The working knowledge is that 
*masterContainer* for AM is null as it itself is the master container.

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

Reply via email to