[
https://issues.apache.org/jira/browse/YARN-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304567#comment-14304567
]
Vinod Kumar Vavilapalli commented on YARN-1983:
-----------------------------------------------
We still need a way to demux the executor to support the case of YARN cluster
with a mix of executors. That'd mean _some_ impact on the CLC, no?
YARN-1964 took the less intrusive way of depending on an env variable in the
container-launch context, shall we continue doing that? My guess is that
exposing richer APIs of specific container-types (instead of the process
oriented CLCs) is better in the long term but too much change in the short term
as the container-space is still going through very fast changes.
> 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)
