You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Artem Harutyunyan (JIRA)" <ji...@apache.org> on 2015/07/08 00:01:05 UTC

[jira] [Updated] (MESOS-2076) Implement maintenance primitives in the Master.

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

Artem Harutyunyan updated MESOS-2076:
-------------------------------------
    Sprint: Mesosphere Sprint 14
    Labels: mesosphere twitter  (was: twitter)

> Implement maintenance primitives in the Master.
> -----------------------------------------------
>
>                 Key: MESOS-2076
>                 URL: https://issues.apache.org/jira/browse/MESOS-2076
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Benjamin Mahler
>              Labels: mesosphere, twitter
>
> The master will need to do a number of things to implement the maintenance primitives:
> # For slaves that have a maintenance window:
> #* For unused resources, offers must be augmented with an Unavailability.
> #* For used resources, inverse offers must be sent.
> # For inverse offers that are declined, we must filter these before sending them again. We must also store the decline reason, guard against OOMing. 
> #* My hunch is that we'll not want to persist the reasons in the initial approach.
> # When the drain window is reached, we'll make a binary decision as to whether the slave was drained, based on whether it was empty.
> #* If drained, we deactivate this slave and store the fact that it was drained.
> #* If not drained, we leave this slave activated.
> # Recover the maintenance information upon failover.



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