[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939069#comment-14939069
]
Vinod Kone commented on MESOS-3563:
-----------------------------------
Looks like this is done intentionally, to preserve backwards compatibility.
https://github.com/apache/mesos/blob/master/src/common/http.cpp#L73
{quote}
// To maintain backwards compatibility we exclude revocable
// resources in the reporting.
{quote}
This was done as part of fixing the resource representation in MESOS-2838. cc
[~xujyan]
> Revocable task CPU shows as zero in /state.json
> -----------------------------------------------
>
> Key: MESOS-3563
> URL: https://issues.apache.org/jira/browse/MESOS-3563
> Project: Mesos
> Issue Type: Bug
> Reporter: Maxim Khutornenko
> Assignee: Vinod Kone
>
> The slave's state.json reports revocable task resources as zero:
> {noformat}
> resources: {
> cpus: 0,
> disk: 3071,
> mem: 1248,
> ports: "[31715-31715]"
> },
> {noformat}
> Also, there is no indication that a task uses revocable CPU. It would be
> great to have this type of info.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
