[MESOS-3128] state.json can not differentiate resources

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 0.22.1
• Fix Version/s: 0.23.0
• Component/s: agent, json api, master
• Assignee: Unassigned
• Reporter: Arvid Warnecke
• Created: 22/Jul/15 14:02
• Updated: 22/Jul/15 17:21
• Resolved: 22/Jul/15 17:21

Description

The information about available resources on the slave listed in the state.json only shows the last set value for a resource.
It is possible to set resources for different mesos roles, but they don't appear in the state.json.

If you set something like this:

cpus(*):24;mem(*):1024;ports(*):[31000-32000];ports(cassandra):[9420]

You get the following in the state.json:

"resources": {
     "cpus": 24,
     "mem": 1024,
     "ports": [9420]
}

Both port ranges in this example are available, but it's difficult to check if your defined resources really are available in Mesos.

Issue Links

• is duplicated by: MESOS-2838 In Resources JSON model() resources of the same name overwrite each other.