[
https://issues.apache.org/jira/browse/MAPREDUCE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427366#comment-13427366
]
Arun C Murthy commented on MAPREDUCE-4334:
------------------------------------------
Alejandro, LCE accomplishes 2 things:
# It serves as a 'root' tool with the setuid bit
# It serves as the home for Linux-specific container maintenance code
Now, for other platforms you have to add other ContainerExecutors anyway for
e.g. branch-1-win has a WindowsTaskController which will be ported over to
trunk as WindowsContainerExecutor.
As, a result, I very much like to continue keeping the Linux-specific bits in
LCE. Furthermore, with native code it is much, much easier to have
platform-specific low-level code i.e. we can use autotools chain to resolve
RHEL5 v/s RHEL6 etc. Doing that via Java plugins is very, very painful and
leads to proliferation of interfaces and configurations. The native code is
something we can deal very easily via Bigtop and other packaging projects.
Thoughts?
> Add support for CPU isolation/monitoring of containers
> ------------------------------------------------------
>
> Key: MAPREDUCE-4334
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4334
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Arun C Murthy
> Assignee: Andrew Ferguson
> Attachments: MAPREDUCE-4334-executor-v1.patch,
> MAPREDUCE-4334-executor-v2.patch, MAPREDUCE-4334-executor-v3.patch,
> MAPREDUCE-4334-executor-v4.patch, MAPREDUCE-4334-pre1.patch,
> MAPREDUCE-4334-pre2-with_cpu.patch, MAPREDUCE-4334-pre2.patch,
> MAPREDUCE-4334-pre3-with_cpu.patch, MAPREDUCE-4334-pre3.patch,
> MAPREDUCE-4334-v1.patch, MAPREDUCE-4334-v2.patch,
> mapreduce-4334-design-doc-v2.txt, mapreduce-4334-design-doc.txt
>
>
> Once we get in MAPREDUCE-4327, it will be important to actually enforce
> limits on CPU consumption of containers.
> Several options spring to mind:
> # taskset (RHEL5+)
> # cgroups (RHEL6+)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
