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

Vinod Kumar Vavilapalli commented on YARN-1983:
-----------------------------------------------

Whatever the approach, we need to have a short/long design write-up.

bq. Policies that select the appropriate executor could demux on the contents 
of the CLC and not a dedicated field.
[~chris.douglas], YARN-1964 does exactly that. It depends on the contents of 
the CLC environment and looks at a specific environment variable. I was 
proposing we continue the same without adding a new CLC field. Are we both 
saying the same thing then?

> 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