hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giovanni Matteo Fumarola (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3828) Add a flag in container to indicate whether it's an AM container or not
Date Thu, 18 Jun 2015 21:55:01 GMT

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

Giovanni Matteo Fumarola commented on YARN-3828:
------------------------------------------------

Thanks [~zjshen] for pointing this out. It is indeed a duplicate as we both need a flag to
identify the AM container but for different reasons :).  Are you planning to work on it soon?
If not I have a patch that I am presently testing with [~subru]and I can go ahead and submit
the patch. The patch is fairly straightforward so it'll be great if you can review it.

> Add a flag in container to indicate whether it's an AM container or not 
> ------------------------------------------------------------------------
>
>                 Key: YARN-3828
>                 URL: https://issues.apache.org/jira/browse/YARN-3828
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Giovanni Matteo Fumarola
>
> YARN-2022 adds a flag in RMContainer to indicate whether the container is an AM or not
to skip pre-emption of AM containers. This JIRA proposes propagating this information to NMs
as it's required by the AMRMProxy (YARN-2884/YARN-3666) to identify if the container is an
AM for:
> 1) Security - for authorizing only AMs to communicate with RMs. For e.g.: this is useful
to prevent DDos attacks by all containers of a malicious app.
> 2) Federation - to allow for transparently spanning an app across multiple sub-clusters



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message