mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-4664) Add allocator metrics.
Date Fri, 12 Feb 2016 15:08:18 GMT

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

Alexander Rukletsov updated MESOS-4664:
---------------------------------------
    Description: 
There are currently no metrics that provide visibility into the allocator, except for the
event queue size. This makes monitoring an debugging allocation behavior in a multi-framework
setup difficult.

Some thoughts for initial metrics to add:

* How many allocation runs have completed? (counter)
* How many allocations each framework got? (counter)
* Current allocation breakdown: allocated / available / total (gauges)
* Current maximum shares (gauges)
* How many active filters are there for the role / framework? (gauges)
* How many frameworks are suppressing offers? (gauges)
* How long does an allocation run take? (timers)
* Maintenance related metrics:
** How many maintenance events are active? (gauges)
** How many maintenance events are scheduled but not active (gauges)
* Quota related metrics:
** How much quota is set for each role? (gauges)
** How much quota is satisfied? How much unsatisfied? (gauges)
 
Some of these are already exposed from the master's metrics, but we should not assume this
within the allocator.

  was:
There are currently no metrics that provide visibility into the allocator, except for the
event queue size. This makes monitoring an debugging allocation behavior in a multi-framework
setup difficult.

Some thoughts for initial metrics to add:

* How many allocation runs have completed? (counter)
* Current allocation breakdown: allocated / available / total (gauges)
* Current maximum shares (gauges)
* How many active filters are there for the role / framework? (gauges)
* How many frameworks are suppressing offers? (gauges)
* How long does an allocation run take? (timers)
* Maintenance related metrics:
** How many maintenance events are active? (gauges)
** How many maintenance events are scheduled but not active (gauges)
* Quota related metrics:
** How much quota is set for each role? (gauges)
** How much quota is satisfied? How much unsatisfied? (gauges)
 
Some of these are already exposed from the master's metrics, but we should not assume this
within the allocator.


> Add allocator metrics.
> ----------------------
>
>                 Key: MESOS-4664
>                 URL: https://issues.apache.org/jira/browse/MESOS-4664
>             Project: Mesos
>          Issue Type: Improvement
>          Components: allocation
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Bannier
>            Priority: Critical
>
> There are currently no metrics that provide visibility into the allocator, except for
the event queue size. This makes monitoring an debugging allocation behavior in a multi-framework
setup difficult.
> Some thoughts for initial metrics to add:
> * How many allocation runs have completed? (counter)
> * How many allocations each framework got? (counter)
> * Current allocation breakdown: allocated / available / total (gauges)
> * Current maximum shares (gauges)
> * How many active filters are there for the role / framework? (gauges)
> * How many frameworks are suppressing offers? (gauges)
> * How long does an allocation run take? (timers)
> * Maintenance related metrics:
> ** How many maintenance events are active? (gauges)
> ** How many maintenance events are scheduled but not active (gauges)
> * Quota related metrics:
> ** How much quota is set for each role? (gauges)
> ** How much quota is satisfied? How much unsatisfied? (gauges)
>  
> Some of these are already exposed from the master's metrics, but we should not assume
this within the allocator.



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

Mime
View raw message