mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Schmiedehausen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2185) slave state endpoint does not contain all resources in the resources field
Date Wed, 31 Dec 2014 03:25:13 GMT

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

Henning Schmiedehausen commented on MESOS-2185:
-----------------------------------------------

This seems like 

- a bug
- an oversight when non-standard resources were added
- an excuse

To be honest, I do not understand why "disk", "mem", "cpu" are treated any special from other
resources (besides the fact that they existed first). To me it seems that the code was not
well refactored when additional resources were added. 

> slave state endpoint does not contain all resources in the resources field
> --------------------------------------------------------------------------
>
>                 Key: MESOS-2185
>                 URL: https://issues.apache.org/jira/browse/MESOS-2185
>             Project: Mesos
>          Issue Type: Bug
>          Components: json api, slave
>    Affects Versions: 0.21.0
>         Environment: Centos 6.5 / Centos 6.6
>            Reporter: Henning Schmiedehausen
>
> fetching status for a slave from the /state.json yields
>   "resources": {
>     "ports": "[31000-32000]",
>     "mem": 512,
>     "disk": 33659,
>     "cpus": 1
>   }
> but in the flags section, it lists
> "flags": {
>    "resources": "cpus:1;mem:512;ports:[31000-32000];set:{label_a,label_b,label_c,label_d};range:[0-1000];scalar:108;numbers:{4,8,15,16,23,42}",
> }
> so there are additional resources. these resources show up when sending offers from that
slave to the frameworks and the frameworks can use and consume them.
> This may just be a reporting issue with the state.json endpoint.
> https://gist.github.com/hgschmie/0dc4f599bb0ff2e815ed is the full response.



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

Mime
View raw message