[ 
https://issues.apache.org/jira/browse/MESOS-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883290#comment-16883290
 ] 

Benjamin Mahler commented on MESOS-8789:
----------------------------------------

{noformat}
commit d6738bcc86525e1ac661d2027a1934134426255f
Author: Benjamin Mahler <bmah...@apache.org>
Date:   Wed Jul 10 19:36:54 2019 -0400

    Added Role::reserved, Role::allocated, Role::offered to master.

    This provides a breakdown of resource quantities on a per-role
    basis, that would aid debugging if shown in the endpoints and
    roles table in the ui.

    Review: https://reviews.apache.org/r/71050
{noformat}

{noformat}
commit 69c8feab6a62b1728872a367a8ed28f88eb029d3 (HEAD -> master, apache/master)
Author: Benjamin Mahler <bmah...@apache.org>
Date:   Wed Jul 10 20:09:31 2019 -0400

    Added reserved, offered, allocated resources to the /roles endpoint.

    This provides helpful information for debugging, as well as for the
    webui to display in the roles table.

    Review: https://reviews.apache.org/r/71053
{noformat}

> Role-related endpoints should display distinct offered and allocated 
> resources.
> -------------------------------------------------------------------------------
>
>                 Key: MESOS-8789
>                 URL: https://issues.apache.org/jira/browse/MESOS-8789
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent, HTTP API, master
>    Affects Versions: 1.5.0
>            Reporter: Till Toenshoff
>            Assignee: Benjamin Mahler
>            Priority: Major
>              Labels: mesosphere, multitenancy, resource-management
>
> The role endpoints currently show accumulated values for resources 
> (allocated), containing offered resources. For gaining an overview showing 
> our allocated resources separately from the offered resources could improve 
> the signal quality, depending on the use case.
> This also affects the UI display, for example the "Roles" tab.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to