You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2018/01/20 01:33:00 UTC
[jira] [Updated] (MESOS-8469) Mesos master might drop some events
in the operator API stream
[ https://issues.apache.org/jira/browse/MESOS-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-8469:
------------------------------
Target Version/s: (was: 1.5.0)
> Mesos master might drop some events in the operator API stream
> --------------------------------------------------------------
>
> Key: MESOS-8469
> URL: https://issues.apache.org/jira/browse/MESOS-8469
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Greg Mann
> Priority: Blocker
>
> Inside `Master::updateTask`, we call `Subscribers::send` which asynchronously calls `Subscribers::Subscriber::send` on each subscriber.
> But the problem is that inside `Subscribers:Subscriber::send` we are looking up the state of the master (e.g., getting Task* and Framework*) which might have changed between `Subscribers::send ` and `Subscribers::Subscriber::send`.
>
> For example, if a terminal task received an acknowledgement the task might be removed from master's state, causing us to drop the TASK_UPDATED event.
>
> We noticed this in an internal cluster, where a TASK_KILLED update was sent to one subscriber but not the other.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)