[
https://issues.apache.org/jira/browse/MAPREDUCE-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420933#comment-13420933
]
Andrew Ferguson commented on MAPREDUCE-4334:
--------------------------------------------
Hi Hari,
In my experiments, there are usually 200-400ms between starting to create the
cgroups and having the process completely inside them. This number is likely an
upper-bound, as the experiments are in pseudo-distributed mode on a VM.
Note that in the design represented by this patch, I move the process into the
cgroup asynchronously, so the latency is not incurred while starting the
process. However, in my reading of Arun's comments, he would prefer that the
cgroups be created synchronously while starting the job. I am currently in the
progress of making this change. While I suspect the cost may not be as high as
200-400ms, it will of course be non-zero. :-)
cheers,
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
