[ https://issues.apache.org/jira/browse/MESOS-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831691#comment-16831691 ]
Vinod Kone commented on MESOS-9761: ----------------------------------- The columns there: "Guarantee" and "Limit" are currently reflecting Quota settings set via quota endpoints. While a reservation for a role technically guarantees that amount to that role (and which is where I assume your confusion stems from) that's currently not the intention of that column. There are plans to improve the quota page in the near future. cc [~mzhu] [~bmahler] > Mesos UI does not properly account for resources set via `--default-role` > ------------------------------------------------------------------------- > > Key: MESOS-9761 > URL: https://issues.apache.org/jira/browse/MESOS-9761 > Project: Mesos > Issue Type: Bug > Reporter: Benno Evers > Priority: Major > Labels: resource-management, ui > Attachments: default_role_ui.png > > > In our cluster, we have two agents configured with > "--default_role=slave_public" and 64 cpus each, for a total of 128 cpus > allocated to this role. The right side of the screenshot shows one of them. > However, looking at the "Roles" tab in the Mesos UI, neither "Guarantee" nor > "Limit" does show any resources for this role. > See attached screenshot for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)