You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2015/11/09 22:30:11 UTC
[jira] [Updated] (MESOS-2081) Add safety constraints for
maintenance primitives.
[ https://issues.apache.org/jira/browse/MESOS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Wu updated MESOS-2081:
-----------------------------
Labels: twitter (was: mesosphere twitter)
> Add safety constraints for maintenance primitives.
> --------------------------------------------------
>
> Key: MESOS-2081
> URL: https://issues.apache.org/jira/browse/MESOS-2081
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Klaus Ma
> Labels: twitter
>
> In order to ensure that the maintenance primitives can be used safely by operators, we want to put a few safety mechanisms in place. Some ideas from the [design doc|https://docs.google.com/a/twitter.com/document/d/16k0lVwpSGVOyxPSyXKmGC-gbNmRlisNEe4p-fAUSojk/]:
> # Prevent bad schedules from being constructed: schedules with more than x% overlap in slaves are rejected.
> # Prevent bad maintenance from proceeding unchecked: if x% of the slaves are not being unscheduled, or are not re-registering, cancel the schedule.
> These will likely be configurable via flags.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)