You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Guangya Liu (JIRA)" <ji...@apache.org> on 2015/11/03 09:22:27 UTC
[jira] [Issue Comment Deleted] (MESOS-2077) Ensure that TASK_LOSTs
for a hard slave drain (SIGUSR1) include a Reason.
[ https://issues.apache.org/jira/browse/MESOS-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guangya Liu updated MESOS-2077:
-------------------------------
Comment: was deleted
(was: A RR is here: https://reviews.apache.org/r/38214)
> Ensure that TASK_LOSTs for a hard slave drain (SIGUSR1) include a Reason.
> -------------------------------------------------------------------------
>
> Key: MESOS-2077
> URL: https://issues.apache.org/jira/browse/MESOS-2077
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: Benjamin Mahler
> Assignee: Guangya Liu
> Labels: twitter
>
> For maintenance, sometimes operators will force the drain of a slave (via SIGUSR1), when deemed safe (e.g. non-critical tasks running) and/or necessary (e.g. bad hardware).
> To eliminate alerting noise, we'd like to add a 'Reason' that expresses the forced drain of the slave, so that these are not considered to be a generic slave removal TASK_LOST.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)