[
https://issues.apache.org/jira/browse/MAPREDUCE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415470#comment-13415470
]
Arun C Murthy commented on MAPREDUCE-4334:
------------------------------------------
{quote}
So, concretely, this is my proposal:
recognize the LCE binary as the "hadoop root tool"
the LCE will have two new functionalities: 1) sched_setaffinity and 2) creating
cgroups
in addition to the patch above, I will create 1) another pluggable
ContainersMonitor which can use these new functions (sched_setaffinity) and 2)
adapt the one above to optionally use the (creating cgroups) functionality of
the "hadoop root tool"
{quote}
Thanks, looks like we finally are on the same page - it's what I've been
proposing for a while now.
Now, it seems like we should enhance the container-launch via LCE to just set
the requisite cgroups or sched_affinity prior-to or right-after the container
launch, rather than make them apis. That would be the safest, no?
> 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-pre1.patch,
> MAPREDUCE-4334-pre2-with_cpu.patch, MAPREDUCE-4334-pre2.patch,
> MAPREDUCE-4334-pre3-with_cpu.patch, MAPREDUCE-4334-pre3.patch
>
>
> 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
