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

ASF GitHub Bot commented on YARN-6668:
--------------------------------------

GitHub user szegedim opened a pull request:

    https://github.com/apache/hadoop/pull/227

    YARN-6668

    YARN-6668 Measure CPU and memory usage with cgroups in ContainersMonitorImpl

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/szegedim/hadoop YARN-6668

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/227.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #227
    
----
commit 2cf0f7c673cd35449f32a4ad337265090d33f07e
Author: Miklos Szegedi <[email protected]>
Date:   2017-06-02T21:55:26Z

    YARN-6668 Add new CGroupsResourceCalculator

commit 1d51e63841fbbff62ad8784ae928aa14f2e36f5c
Author: Miklos Szegedi <[email protected]>
Date:   2017-06-06T20:27:59Z

    YARN-6668 Add new CGroupsResourceCalculator

----


> Use cgroup to get container resource utilization
> ------------------------------------------------
>
>                 Key: YARN-6668
>                 URL: https://issues.apache.org/jira/browse/YARN-6668
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Haibo Chen
>            Assignee: Miklos Szegedi
>
> Container Monitor relies on proc file system to get container resource 
> utilization, which is not as efficient as reading cgroup accounting. We 
> should in NM, when cgroup is enabled, read cgroup stats instead. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to