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

Chris Douglas commented on YARN-1983:
-------------------------------------

bq. 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?

Policies that select the appropriate executor could demux on the contents of 
the CLC and not a dedicated field. A simple, static dispatch from an 
admin-configured list is a great place to start, but adding a string to the CLC 
that selects the executor class by name is difficult to evolve. Since the same 
semantics are available without changes to the platform, why bake these in?

bq. I think my current patch is intrusive indeed but more general, right?

I'm not sure I follow. How is it more general?

> 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