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

Ignore launch/kill requests in the slave originating from non-leading masters.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.16.0
    • Component/s: agent
    • Labels:
      None

      Description

      These were left as TODOs in the code when applying a related fix:

      void Slave::runTask(
      const FrameworkInfo& frameworkInfo,
      const FrameworkID& frameworkId,
      const string& pid,
      const TaskInfo& task)
      {
      // TODO(bmahler): Consider ignoring requests not originating from the
      // expected master.

      void Slave::killTask(const FrameworkID& frameworkId, const TaskID& taskId)
      {
      // TODO(bmahler): Consider ignoring requests not originating from the
      // expected master.

      We've observed a scenario in which a non-leading master flushed it's queue of messages before committing suicide, the framework in this case launched the same task twice, but regardless we should ignore these messages in the slave.

        Attachments

          Activity

            People

            • Assignee:
              bmahler Benjamin Mahler
              Reporter:
              bmahler Benjamin Mahler
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: