[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14943073#comment-14943073
]
Qian Zhang commented on MESOS-3563:
---
I think #2 might be better since that way user will have a full view all all
the resources in the "resources" object.
> 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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939021#comment-14939021
]
Niklas Quarfot Nielsen commented on MESOS-3563:
---
Can you share the full state.json?
> 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
>
> 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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939046#comment-14939046
]
Maxim Khutornenko commented on MESOS-3563:
--
Correct, fixed resource estimator.
> 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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939044#comment-14939044
]
Niklas Quarfot Nielsen commented on MESOS-3563:
---
I didn't understand the full context of your problem; assume you are using the
fixed resource estimator? At any regard, looks like Vinod is on it.
> 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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939030#comment-14939030
]
Maxim Khutornenko commented on MESOS-3563:
--
It's just too big to sanitize :) Is there anything in particular you are
interested in?
> 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)
[jira] [Commented] (MESOS-3563) Revocable task CPU shows as zero in /state.json
[
https://issues.apache.org/jira/browse/MESOS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
