[
https://issues.apache.org/jira/browse/HADOOP-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6961.
--------------------------------------
Resolution: Won't Fix
I'm going to close this as Won't Fix. Here's why:
With YARN (and even under 1.x), the task launcher stuff is pluggable. If one
wanted to integrate KVM or some other virtualization support, the hooks are
basically there now. Out of the box, cgroup support is there. If YARN-1964
moves forward, then Hadoop will have support for Docker-style containers as
well.
So this JIRA is better off being refiled as using a specific technology rather
than something generic.
> Integration of Virtualization (such as Xen) with Hadoop tools
> -------------------------------------------------------------
>
> Key: HADOOP-6961
> URL: https://issues.apache.org/jira/browse/HADOOP-6961
> Project: Hadoop Common
> Issue Type: New Feature
> Environment: All
> Reporter: Saikat Kanjilal
> Priority: Minor
>
> How does one integrate sandboxing of arbitrary user code in C++ and other
> languages in a VM such as Xen with the Hadoop framework? How does this
> interact with SGE, Torque, Condor?
> As each individual machine has more and more cores/cpus, it makes sense to
> partition each machine into multiple virtual machines. That gives us a number
> of benefits:
> By assigning a virtual machine to a datanode, we effectively isolate the
> datanode from the load on the machine caused by other processes, making the
> datanode more responsive/reliable.
> With multiple virtual machines on each machine, we can lower the granularity
> of hod scheduling units, making it possible to schedule multiple tasktrackers
> on the same machine, improving the overall utilization of the whole clusters.
> With virtualization, we can easily snapshot a virtual cluster before
> releasing it, making it possible to re-activate the same cluster in the
> future and start to work from the snapshot.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
