[ https://issues.apache.org/jira/browse/MAPREDUCE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420363#comment-13420363 ]
Bikas Saha commented on MAPREDUCE-4334: --------------------------------------- Aside from a design proposal I would be really interested in seeing how exactly cgroups work in the context of our typical workload. Say, take a bunch of typical mappers and reducers and run them in isolation. Then run them in isolation within cgroups. Is there a difference? Now run them concurrently with and without cgroups. What are the observations? These experiments may lead to expected or unexpected results and would be a great addition to the design pros and cons. Perhaps you have already run those experiments. If yes, care sharing the results. > 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