You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benno Evers (JIRA)" <ji...@apache.org> on 2018/06/15 11:21:00 UTC

[jira] [Created] (MESOS-9000) Operator API event stream can miss task status updates

Benno Evers created MESOS-9000:
----------------------------------

             Summary: Operator API event stream can miss task status updates
                 Key: MESOS-9000
                 URL: https://issues.apache.org/jira/browse/MESOS-9000
             Project: Mesos
          Issue Type: Bug
            Reporter: Benno Evers


As of now, the master only sends TaskUpdated messages
to subscribers when the latest known task state on the agent changed.

{noformat}
// src/messages/messages.proto
message StatusUpdate {
  [...]
  // This corresponds to the latest state of the task according to the
  // agent. Note that this state might be different than the state in
  // 'status' because task status update manager queues updates. In
  // other words, 'status' corresponds to the update at top of the
  // queue and 'latest_state' corresponds to the update at bottom of
  // the queue.
  optional TaskState latest_state = 7;
}
{noformat}

This implied that schedulers could not reliably wait for the status
information corresponding to specific state updates (i.e. TASK_RUNNING),
since there is no guarantee that subscribers get notified during
the time when this status update will be included in the status field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)