mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guangya Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-4123) Added USAGE_SLACK metrics to snapshot endpoint for master/agent
Date Sun, 03 Jan 2016 13:39:39 GMT

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

Guangya Liu updated MESOS-4123:
-------------------------------
    Description: 
The master/agent have endpoint to get all revocable resources but the current revocable resources
will include both usage slack and allocation slack resources.

It is better to put usage slack metrics to 

  was:
Now the master/agent have endpoint to get all revocable resources but the current revocable
resources are only for QoS controller.

The current use of those resource are only for some display issues, but we may need those
APIs in future such as MESOS-2647 , it need to calculate if there are enough usage_slack revocable
resources before launch a task.

So I think that we need to update the helper functions of
{code}_resources_revocable_total{code}
{code}_resources_revocable_used{code}
{code}_resources_revocable_percent{code}
to only get usage_slack revocable resources .


> Added USAGE_SLACK metrics to snapshot endpoint for master/agent
> ---------------------------------------------------------------
>
>                 Key: MESOS-4123
>                 URL: https://issues.apache.org/jira/browse/MESOS-4123
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Guangya Liu
>            Assignee: Guangya Liu
>
> The master/agent have endpoint to get all revocable resources but the current revocable
resources will include both usage slack and allocation slack resources.
> It is better to put usage slack metrics to 



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

Mime
View raw message