mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MESOS-758) Incorrect memory statistics are reported under linux
Date Tue, 12 Nov 2013 23:35:21 GMT

     [ https://issues.apache.org/jira/browse/MESOS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Mahler resolved MESOS-758.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.15.0
         Assignee: Eric W. Biederman

Submitted patches:

https://reviews.apache.org/r/14825/
https://reviews.apache.org/r/15013/
https://reviews.apache.org/r/15015/

> Incorrect memory statistics are reported under linux
> ----------------------------------------------------
>
>                 Key: MESOS-758
>                 URL: https://issues.apache.org/jira/browse/MESOS-758
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.12.0, 0.13.0, 0.14.0, 0.14.1, 0.14.2
>            Reporter: Eric W. Biederman
>            Assignee: Eric W. Biederman
>             Fix For: 0.15.0
>
>
> Under linux when using the cgroup_isolator only the number of non file backed pages are
reported in the memory rss.  This excludes all text pages in the binaries and all page cache
pages.   As a result of the incorrect reporting users are very confused when they hit their
memory limits when it appears they are gigabytes away from them.
> The correct number to report is from the file memory.usage_in_bytes.
> It would also be nice to have:
> memory.stat:total_rss -- This is the number of bytes that are not backed by files.
> memory.stat:total_cached -- This is the number of bytes that are backed by files.
> memory.stat:total_mapped -- This is the number of bytes backed by files that are mmaped
into processes.  
> memory.stat:rss that is currently reported is wrong in two dimensions.
> - It does not include child cgroups
> - It does not include any file backed pages, so it is strictly impossible to run the
job with the limit set to the number that is reported.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message