You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2015/06/19 00:08:01 UTC

[jira] [Resolved] (YARN-3116) [Collector wireup] We need an assured way to determine if a container is an AM container on NM

     [ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhijie Shen resolved YARN-3116.
-------------------------------
    Resolution: Duplicate

Close this jira as the duplicate of YARN-3828, whether the contributor has already started working on the issue.

> [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: Zhijie Shen
>
> 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)