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

Yan Xu commented on MESOS-2776:
-------------------------------

h2. State

h3. Resources model change
Current resources are exported like this:

{noformat:title=}
resources: {
cpus: 0.210000000000001,
disk: 389429,
ephemeral_ports: "[32768-57344]",
mem: 57402,
ports: "[31697-31708, 31966-31969, 31971-32000, 31500-31695, 31907-31964, 
31761-31905, 31083-31428, 31710-31759, 31000-31081, 31430-31498]"
},
{noformat}

Revocable resources can look like this:
{noformat:title=}
resources: {
cpus{REV}: 0.210000000000001,
disk{REV}: 389429,
ephemeral_ports{REV}: "[32768-57344]",
mem{REV}: 57402,
ports{REV}: "[31697-31708, 31966-31969, 31971-32000, 31500-31695, 31907-31964, 
31761-31905, 31083-31428, 31710-31759, 31000-31081, 31430-31498]"
},
{noformat}
a la https://reviews.apache.org/r/34676

h4. Notes
- *Regular resources will look the same*.
- Since regular resources and revocable resources can't be merged, the 
'resources' dict will separately list them all. 

This will change the resources representations used by different models in 
state.json:
Slave: used_resources, offered_resources
Task: resources
Framework: offered_resources

h3. Framework model change: capabilities 
{noformat:title=}
capabilities : {
  revocable: true
}
{noformat}

Changes can be made just to the JOSN model. Framework struct in Master doesn't 
need to change.

> Master should expose metrics about oversubscribed resources
> -----------------------------------------------------------
>
>                 Key: MESOS-2776
>                 URL: https://issues.apache.org/jira/browse/MESOS-2776
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Vinod Kone
>            Assignee: Yan Xu
>
> state.json and metrics/snapshot should expose metrics on oversubscribed 
> resources (allocated and available).



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

Reply via email to