[
https://issues.apache.org/jira/browse/MAPREDUCE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420347#comment-13420347
]
Andrew Ferguson commented on MAPREDUCE-4334:
--------------------------------------------
Hi Arun,
I feel like we've been discussing pros & cons for the length of this JIRA. :-)
I think, perhaps, I proposed too large of a change across this issue and
MAPREDUCE-4351: cgroups for cpu, cgroups for memory, a code refactoring, etc.
Instead, I would like to make a smaller change, with just cgroups for CPUs and
place them in each launcher's code, as you requested above. Perhaps a better
re-factoring than I suggested with the ContainersMonitor will become clear
afterwards.
How does this sound to you? I was planning to finish it up on Monday.
best,
Andrew
> 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,
> MAPREDUCE-4334-v1.patch, MAPREDUCE-4334-v2.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
