[
https://issues.apache.org/jira/browse/MESOS-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575475#comment-14575475
]
Benjamin Mahler commented on MESOS-2753:
----------------------------------------
Disallowing mixing seems to be the easiest solution from the framework
implementation perspective. This means your executor and task are resources can
independent of the distribution of resources in the offer: _you don't need to
figure out how to mix resources from the offer to correctly launch a
best-effort task_.
There is a subtlety around disallowing the mixing of resources. For example,
let's say that you're only receiving non-revocable cpus, but you have
best-effort tasks that you want to launch? You won't find any matching
resources for these in the offers since you're only receiving non-revocable
cpus!
To address this, it would be ideal for estimators to ensure that they include
total unused resources on the slave, not just allocated resources that are
unused. That way, schedulers will receive revocable resources without having to
wait for allocated resources to become unused. Make sense?
> Master should validate tasks using oversubscribed resources
> -----------------------------------------------------------
>
> Key: MESOS-2753
> URL: https://issues.apache.org/jira/browse/MESOS-2753
> Project: Mesos
> Issue Type: Task
> Components: isolation, master
> Affects Versions: 0.23.0
> Reporter: Ian Downes
> Assignee: Vinod Kone
> Labels: twitter
>
> Current implementation out for [review|https://reviews.apache.org/r/34310]
> only supports setting the priority of containers with revocable CPU if it's
> specified in the initial executor info resources. This should be enforced at
> the master.
> Also master should make sure that oversubscribed resources used by the task
> are valid.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
