You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2018/07/04 01:04:00 UTC
[jira] [Commented] (MESOS-8982) add cgroup
memory.max_usage_in_bytes into slave monitor/statistics endpoint
[ https://issues.apache.org/jira/browse/MESOS-8982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532112#comment-16532112 ]
Benjamin Mahler commented on MESOS-8982:
----------------------------------------
FYI [~gilbert] [~qianzhang]
> add cgroup memory.max_usage_in_bytes into slave monitor/statistics endpoint
> ---------------------------------------------------------------------------
>
> Key: MESOS-8982
> URL: https://issues.apache.org/jira/browse/MESOS-8982
> Project: Mesos
> Issue Type: Improvement
> Components: cgroups, docker, HTTP API
> Affects Versions: 1.6.0
> Reporter: Martin Bydzovsky
> Priority: Minor
>
> As an operator, I'm periodically checking slave's monitor/statistics endpoint to get the memory/cpu usage/cpu throttle for each running task. However, if there is a short-term memory usage peak (lets say seconds), I might miss it (the memory might have been allocated and also released in between my 2 collect-metrics intervals). Since the max used memory is logged in the `/sys/fs/cgroup/memory/docker/CID/memory.max_usage_in_bytes`, it would be great, if this info would have been exposed in the api as well..
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)