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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/06/19 02:31:01 UTC
[jira] [Resolved] (YARN-3828) Add a flag in container to indicate
whether it's an AM container or not
[ https://issues.apache.org/jira/browse/YARN-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved YARN-3828.
-------------------------------------------
Resolution: Duplicate
We usually close the newly filed JIRAs as dups.
I am closing this as dup of YARN-3116 and assigning that to [~giovanni.fumarola].
> 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)