hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers
Date Sun, 28 Oct 2012 05:11:15 GMT

    [ https://issues.apache.org/jira/browse/YARN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485570#comment-13485570
] 

Bikas Saha commented on YARN-3:
-------------------------------

Why is mountCGroups a method in LinuxContainerExecutor code? Shouldn't CgroupsLCEResourcesHandler
completely abstract out everything about cgroups?
{code}
+  public boolean mountCgroups(List<String> cgroupKVs, String hierarchy) {
{code}

It would be really great to add more tests. This is a fairly non-trivial piece of functionality.
So having more functional tests that verify cgroups, limits, killing etc are working as expected
would help a ton in guarding against bugs and regressions.

What will happen if we use cgroups to limit CPU but there is only 1 container running on a
machine. Will the container be able to access all the CPU until other tasks start running?
                
> Add support for CPU isolation/monitoring of containers
> ------------------------------------------------------
>
>                 Key: YARN-3
>                 URL: https://issues.apache.org/jira/browse/YARN-3
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun C Murthy
>            Assignee: Andrew Ferguson
>         Attachments: mapreduce-4334-design-doc.txt, mapreduce-4334-design-doc-v2.txt,
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.patch, MAPREDUCE-4334-pre2-with_cpu.patch,
MAPREDUCE-4334-pre3.patch, MAPREDUCE-4334-pre3-with_cpu.patch, MAPREDUCE-4334-v1.patch, MAPREDUCE-4334-v2.patch,
YARN-3-lce_only-v1.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message