Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-2077

Ensure that TASK_LOSTs for a hard slave drain (SIGUSR1) include a Reason.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Reviewable
    • Major
    • Resolution: Unresolved
    • None
    • None
    • agent, master

    Description

      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.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. MESOS-3265 Starting maintenance needs to deactivate agents and kill tasks.

          • Major - Major loss of function.
          • Resolved
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-9298 Task failures sometimes can't be understood without looking into agent logs.

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-1475 Provide a way to fully shut down a slave (kill all tasks underneath).

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              gyliu Guangya Liu
              bmahler Benjamin Mahler
              Benjamin Mahler Benjamin Mahler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: