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 2015/01/22 01:18:35 UTC

[jira] [Updated] (MESOS-2234) Restarting slave with docker containerizer causes statistics to be inaccurate.

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

Benjamin Mahler updated MESOS-2234:
-----------------------------------
    Component/s: docker
        Summary: Restarting slave with docker containerizer causes statistics to be inaccurate.  (was: Restarting slave process causes statistics to be inaccurate)

(Updated this to reflect it's the docker containerizer).

> Restarting slave with docker containerizer causes statistics to be inaccurate.
> ------------------------------------------------------------------------------
>
>                 Key: MESOS-2234
>                 URL: https://issues.apache.org/jira/browse/MESOS-2234
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker, json api, slave, statistics
>    Affects Versions: 0.21.0
>         Environment: Mesos 0.21.0
> Marathon 0.7.6
> Docker 1.4.1
>            Reporter: Markus Meyer
>            Priority: Minor
>
> The endpoint {{/monitor/statistics.json}} of a slave reports inaccurate data after restarting the slave process.
> For example, the {{mem_rss_bytes}} field of a task reports a value of about 200MB before the restart. After restarting the slave, the task is reported to use 42MB and that value does not change over time.
> All tasks use the Docker containerizer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)