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

Chun Chen commented on YARN-1983:
---------------------------------

[~vinodkv], according to your suggestion, I propose the following change: 
1. Allow NM_CE to specify a comma list CE classes.
2. Allow user to specify a env named NM_CLIENT_CE in CLC. If the value of 
NM_CLIENT_CE is one of the CE class configured previous, choose that one to 
execute the container, throw exception otherwise.
3. If user specify only one CE class of NM_CE, ignore NM_CLIENT_CE in env of 
CLC and always use that one to execute containers.
4. If user specify multiple classes of NM_CE, he has to configure for a default 
CE named NM_DEFAULT_CE in yarn-site.xml in case he doesn't specify env 
NM_CLIENT_CE on submit containers.

NM_CE=yarn.nodemanager.container-executor.class
NM_CLIENT_CE=yarn.nodemanager.client.container-executor.class
NM_DEFAULT_CE=yarn.nodemanager.default.container-executor.class

> Support heterogeneous container types at runtime on YARN
> --------------------------------------------------------
>
>                 Key: YARN-1983
>                 URL: https://issues.apache.org/jira/browse/YARN-1983
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Junping Du
>         Attachments: YARN-1983.2.patch, YARN-1983.patch
>
>
> Different container types (default, LXC, docker, VM box, etc.) have different 
> semantics on isolation of security, namespace/env, performance, etc.
> Per discussions in YARN-1964, we have some good thoughts on supporting 
> different types of containers running on YARN and specified by application at 
> runtime which largely enhance YARN's flexibility to meet heterogenous app's 
> requirement on isolation at runtime.



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

Reply via email to