[
https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975599#comment-13975599
]
jay vyas commented on YARN-1964:
--------------------------------
This takes us away from the java idiom of packaging apps as jars .... Its a
pretty bold step so let me play devils advocate, because I think it might not
be the best idea.
1) Tying yarn's JVM NodeManagers to LCE's adds a new dependency to the YARN
stack. adds new building/compiling/maintaining costs.
2) NodeManagers are being run in LinuxContainers quite commonly. This could
lead to containers, launching NM's, which again launch containers. Seems
kind of yucky dont you think?
3) It forces yarn to be aware of linux containers. This might lead to
encouraging the creation of application code that doesnt run easily outside of
containerized environment. As awesome as LCE's are, most java and bigdata apps
running in YARN with the hadoop .
> Support Docker containers in YARN
> ---------------------------------
>
> Key: YARN-1964
> URL: https://issues.apache.org/jira/browse/YARN-1964
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
>
> Docker (https://www.docker.io/) is, increasingly, a very popular container
> technology.
> In context of YARN, the support for Docker will provide a very elegant
> solution to allow applications to *package* their software into a Docker
> container (entire Linux file system incl. custom versions of perl, python
> etc.) and use it as a blueprint to launch all their YARN containers with
> requisite software environment. This provides both consistency (all YARN
> containers will have the same software environment) and isolation (no
> interference with whatever is installed on the physical machine).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
