Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 3 May 2014 23:28:17 +0000 (UTC)
From: "Abin Shahab (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12710452.1398381560498.226112.1399159697087@arcas>
In-Reply-To: <JIRA.12710452.1398381560498@arcas>
References: <JIRA.12710452.1398381560498@arcas>
Subject: [jira] [Commented] (YARN-1983) Support heterogeneous container
 types at runtime on YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abin Shahab commented on YARN-1983:
-----------------------------------

I'm assuming we'll still be using a generic container executor for this(among other things). Shall we refer to this executor as GenericContainerExecutor?

> 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
>
> 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.2#6252)