[
https://issues.apache.org/jira/browse/MESOS-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371243#comment-15371243
]
Joseph Wu commented on MESOS-5824:
----------------------------------
Not sure why this would be backported?
If I recall correctly, the resources string was passed between versions of
Mesos, but this should no longer be the case. That's why I was wondering about
backwards compatibility.
> Include disk source information in stringification
> --------------------------------------------------
>
> Key: MESOS-5824
> URL: https://issues.apache.org/jira/browse/MESOS-5824
> Project: Mesos
> Issue Type: Improvement
> Components: stout
> Affects Versions: 0.28.2
> Reporter: Tim Harper
> Priority: Minor
> Labels: mesosphere
> Fix For: 1.1.0
>
> Attachments: 0001-Output-disk-resource-source-information.patch
>
>
> Some frameworks (like kafka_mesos) ignore the Source field when trying to
> reserve an offered mount or path persistent volume; the resulting error
> message is bewildering:
> {code:none}
> Task uses more resources
> cpus(*):4; mem(*):4096; ports(*):[31000-31000]; disk(kafka,
> kafka)[kafka_0:data]:960679
> than available
> cpus(*):32; mem(*):256819; ports(*):[31000-32000]; disk(kafka,
> kafka)[kafka_0:data]:960679; disk(*):240169;
> {code}
> The stringification of disk resources should include source information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
