[
https://issues.apache.org/jira/browse/MESOS-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980931#comment-15980931
]
Alexander Rukletsov commented on MESOS-7375:
--------------------------------------------
[~bmahler], [~klueska] I remember there was a discussion of introducing a
notion of “scarce” resources. This sounds like a possible solution to this
problem: by default, GPU resources are considered normal and everyone gets them
offered, but if an operator marks them as scarce we stop offering agents with
these resoruces unless a framework opts in (current behaviour).
> provide additional insight for framework developers re: GPU_RESOURCES
> capability
> --------------------------------------------------------------------------------
>
> Key: MESOS-7375
> URL: https://issues.apache.org/jira/browse/MESOS-7375
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Reporter: James DeFelice
> Labels: mesosphere
>
> On clusters where all nodes are equal and every node has a GPU, frameworks
> that **don't** opt-in to the `GPU_RESOURCES` capability won't get any offers.
> This is surprising for operators.
> Even when a framework doesn't **need** GPU resources, it may make sense for a
> framework scheduler to provide a `--gpu-cluster-compat` (or similar) flag
> that results in the framework advertising the `GPU_RESOURCES` capability even
> though it does not intend to consume any GPU. The effect being that said
> framework will now receive offers on clusters where all nodes have GPU
> resources.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
