[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939096#comment-14939096
]
Vinod Kone commented on MESOS-3563:
-----------------------------------
So I think we could/should add the revocable resources information in the
endpoints that display "Resources".
Couple of options
#1: have a different "revocable_resources" object in addition to the
"resources" object in the JSON.
{code}
revocable_resources: {
cpus: 2,
...
}
{code}
#2: keep one "resources" object but add new keys "cpus_revocable"
{code}
resources : {
cpus: 2,
cpus_revocable: 2,
...
}
{code}
Any preferences? #1 seems easier to implement and maintain. #2 seems closer to
what /metrics/snapshot has (slave/cpus_total, slave/cpus_revocable_total)
> 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)
