hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3116) [Aggregator wireup] We need an assured way to determine if a container is an AM container on NM
Date Mon, 02 Mar 2015 15:34:07 GMT

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

Junping Du commented on YARN-3116:
----------------------------------

I think we can consider to add an optional field in ContainerLaunchContext, so AMLauncher
inside of RM can set this value different from launching normal containers. It then get passed
to ContainerImpl, so ContainerInitializationContext in AuxiliaryService can aware it. Thoughts

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