You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Chun Chen (JIRA)" <ji...@apache.org> on 2015/01/27 07:44:37 UTC

[jira] [Commented] (YARN-1983) Support heterogeneous container types at runtime on YARN

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

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

Attach a patch which creates a CompositeContainerExecutor to implement this. The patch allows apps to specify container executor class in ContainerLaunchContext. Also changes ${yarn.nodemanager.container-executor.class} to allow specify a comma separated list of container executor class and adds a new configuration ${yarn.nodemanager.default.container-executor.class}, the default container executor to execute(launch) the containers when submit containers without specify container executor.

> 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.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)