mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From " (Commented) (JIRA)" <>
Subject [jira] [Commented] (MESOS-89) create utilities to collect information from the proc filesystem
Date Thu, 08 Dec 2011 00:02:42 GMT

] commented on MESOS-89:

This is an automatically generated e-mail. To reply, visit:

(Updated 2011-12-08 00:00:32.699023)

Review request for mesos.


I've address the comments and updated the diff. PTAL.


The first of several patches related to resource usage monitoring. This patch provides a collection
of utilities for use on Linux for reading stats from proc. It is used by both the lxc and
proc resource collectors.

This addresses bug MESOS-89.

Diffs (updated)

  src/tests/ ea943f7 
  src/tests/proc_utils_tests.cpp PRE-CREATION 
  src/monitoring/proc_utils.cpp PRE-CREATION 
  src/ 516f128 
  src/monitoring/proc_utils.hpp PRE-CREATION 



Sanity tests have been written in src/tests/proc_utils_tests.cpp for all utility functions,
and functions have been tested ad hoc.



> create utilities to collect information from the proc filesystem
> ----------------------------------------------------------------
>                 Key: MESOS-89
>                 URL:
>             Project: Mesos
>          Issue Type: Sub-task
>          Components: slave
>         Environment: This is specific to Linux, as OS X does not have a proc filesystem.
>            Reporter: Sam Whitlock
>            Assignee: Alex Degtiar
>            Priority: Minor
>              Labels: monitoring
> This is a utility for MESOS-38
> Create a collection of utilities to read information from the proc filesystem. This will
be used in MESOS-38 to collect most of the information for the process-based isolation usage
reporting mechanism. These utilities will also be used for certain functionality in monitoring
lxc-based isolation because not all of the information needed is available via the cgroup
interface, such as the start time of the container.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message