[
https://issues.apache.org/jira/browse/MESOS-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105443#comment-15105443
]
Qian Zhang commented on MESOS-4392:
-----------------------------------
{quote}
Revoking a SINGLE accepted oversubscription offer for a resource cannot make
the resource non-revocable, because another task may be holding on to its
actual physical assets. Only revoking the "regular" offer that claims the same
resource would create a clear enough picture to assign the resource as
non-revocable to a new primary "owner". We'd then rely on the QoS mechanism to
satisfy the needs of the latter in case a third, revocable offer were currently
using the resource.
{quote}
I am not sure if I get your point, here is my understanding with an example:
framework1 launches task1 with a regular offer, but that task is not fully
using the resources, and the unused part of the resources are reported by
resource estimator as revocable resources and offered to framework 2, and
framework 2 launches task2 with that revocable offer. In this case, revoking
task2 of framework 2 is not enough to make the resources non-revocable because
task 1 of framework 1 is also using the resources, so we should also revoke
task1 of framework1 in this case?
> Balance quota frameworks with non-quota, greedy frameworks.
> -----------------------------------------------------------
>
> Key: MESOS-4392
> URL: https://issues.apache.org/jira/browse/MESOS-4392
> Project: Mesos
> Issue Type: Epic
> Components: allocation, master
> Reporter: Bernd Mathiske
> Assignee: Alexander Rukletsov
> Labels: mesosphere
>
> Maximize resource utilization and minimize starvation risk for both quota
> frameworks and non-quota, greedy frameworks when competing with each other.
> A greedy analytics batch system wants to use as much of the cluster as
> possible to maximize computational throughput. When a competing web service
> with fixed task size starts up, there must be sufficient resources to run it
> immediately. The operator can reserve these resources by setting quota.
> However, if these resources are kept idle until the service is in use, this
> is wasteful from the analytics job's point of view. On the other hand, the
> analytics job should hand back reserved resources to the service when needed
> to avoid starvation of the latter.
> We can assume that often, the resources needed by the service will be of the
> non-revocable variety. Here we need to introduce clearer distinctions between
> oversubscribed and revocable resources that are not oversubscribed. An
> oversubscribed resource cannot be converted into a non-revocable resource,
> not even by preemption. In contrast, a non-oversubscribed, revocable resource
> can be converted into a non-revocable resource.
> Another related topic is optimistic offers. The pertinent aspect in this
> context is again whether resources are oversubscribed or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
