You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2015/02/17 21:12:12 UTC

[jira] [Resolved] (MESOS-2185) slave state endpoint does not contain all resources in the resources field

     [ https://issues.apache.org/jira/browse/MESOS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominic Hamon resolved MESOS-2185.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.22.0

commit 73ddc21f44e65499d4179bb15edf97243c8ab18c (HEAD, origin/master, origin/HEAD, master)
Author: Joerg Schad <jo...@mesosphere.io>
Commit: Dominic Hamon <dm...@twitter.com>

    Included all resources in state endpoint.
    
    Review: https://reviews.apache.org/r/31082

> 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
>            Assignee: Joerg Schad
>              Labels: mesosphere
>             Fix For: 0.22.0
>
>
> 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)