You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Ian Downes (JIRA)" <ji...@apache.org> on 2015/06/08 20:23:08 UTC

[jira] [Resolved] (MESOS-2817) Support revocable/non-revocable CPU updates in Mesos containerizer

     [ https://issues.apache.org/jira/browse/MESOS-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Downes resolved MESOS-2817.
-------------------------------
    Resolution: Won't Fix

Consensus is to only support a single resource being entirely revocable/non-revocable so the behavior is intuitive and therefore the existing code for the CPU isolator is sufficient.

> Support revocable/non-revocable CPU updates in Mesos containerizer
> ------------------------------------------------------------------
>
>                 Key: MESOS-2817
>                 URL: https://issues.apache.org/jira/browse/MESOS-2817
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>    Affects Versions: 0.23.0
>            Reporter: Ian Downes
>            Assignee: Ian Downes
>              Labels: twitter
>
> MESOS-2652 provided preliminary support for revocable cpu resources only when specified in the initial resources for a container. Improve this to support updates to/from revocable cpu. Note, *any* revocable cpu will result in the entire container's cpu being treated as revocable at the cpu isolator level. Higher level logic is responsible for adding/removing based on some policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)