[
https://issues.apache.org/jira/browse/MESOS-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106688#comment-15106688
]
Niklas Quarfot Nielsen commented on MESOS-2930:
-----------------------------------------------
Hi [~bmahler] - sorry for the super tardy reply.
For Serenity, the Estimator and QoS controllers acts as edges on a shared
pipeline of filters (lives in it's own actor). In short, the estimator pushes
usage statistics in and awaits estimates, whereas the QoS controller awaits
corrections from the pipeline.
> Allow the Resource Estimator to express over-allocation of revocable
> resources.
> -------------------------------------------------------------------------------
>
> Key: MESOS-2930
> URL: https://issues.apache.org/jira/browse/MESOS-2930
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Benjamin Mahler
> Assignee: Klaus Ma
>
> Currently the resource estimator returns the amount of oversubscription
> resources that are available, since resources cannot be negative, this allows
> the resource estimator to express the following:
> (1) Return empty resources: We are fully allocated for oversubscription
> resources.
> (2) Return non-empty resources: We are under-allocated for oversubscription
> resources. In other words, some are available.
> However, there is an additional situation that we cannot express:
> (3) Analogous to returning non-empty "negative" resources: We are
> over-allocated for oversubscription resources. Do not re-offer any of the
> over-allocated oversubscription resources that are recovered.
> Without (3), the slave can only shrink the total pool of oversubscription
> resources by returning (1) as resources are recovered, until the pool is
> shrunk to the desired size. However, this approach is only best-effort, it's
> possible for a framework to launch more tasks in the window of time (15
> seconds by default) that the slave polls the estimator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
