You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2016/07/09 10:49:12 UTC
[jira] [Updated] (MESOS-3889) Modify Oversubscription documentation
to explicitly forbid the QoS Controller from killing executors running on
optimistically offered resources.
[ https://issues.apache.org/jira/browse/MESOS-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Klaus Ma updated MESOS-3889:
----------------------------
Assignee: (was: Klaus Ma)
> Modify Oversubscription documentation to explicitly forbid the QoS Controller from killing executors running on optimistically offered resources.
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-3889
> URL: https://issues.apache.org/jira/browse/MESOS-3889
> Project: Mesos
> Issue Type: Bug
> Reporter: Artem Harutyunyan
> Labels: mesosphere
>
> The oversubcription documentation currently assumes that oversubscribed resources ({{USAGE_SLACK}}) are the only type of revocable resources. Optimistic offers will add a second type of revocable resource ({{ALLOCATION_SLACK}}) that should not be acted upon by oversubscription components.
> For example, the [oversubscription doc|http://mesos.apache.org/documentation/latest/oversubscription/] says the following:
> {quote}
> NOTE: If any resource used by a task or executor is revocable, the whole container is treated as a revocable container and can therefore be killed or throttled by the QoS Controller.
> {quote}
> which we may amend to something like:
> {quote}
> NOTE: If any resource used by a task or executor is revocable usage slack, the whole container is treated as an oversubscribed container and can therefore be killed or throttled by the QoS Controller.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)