hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3116) [Aggregator wireup] We need an assured way to determine if a container is an AM container on NM
Date Wed, 11 Feb 2015 23:16:12 GMT

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

Vinod Kumar Vavilapalli updated YARN-3116:
------------------------------------------
    Summary: [Aggregator wireup] We need an assured way to determine if a container is an
AM container on NM  (was: We need an assured way to determine if a container is an AM container
on NM)

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

Mime
View raw message