You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anindya Sinha (JIRA)" <ji...@apache.org> on 2016/05/06 23:44:12 UTC

[jira] [Updated] (MESOS-5143) LostSlaveMessage should not be broadcasted.

     [ https://issues.apache.org/jira/browse/MESOS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anindya Sinha updated MESOS-5143:
---------------------------------
    Shepherd: Yan Xu

> LostSlaveMessage should not be broadcasted.
> -------------------------------------------
>
>                 Key: MESOS-5143
>                 URL: https://issues.apache.org/jira/browse/MESOS-5143
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>            Reporter: Yan Xu
>            Assignee: Anindya Sinha
>
> Currently a {{LostSlaveMessage}} (in v1 it's a type of {{Event::Failure}}) is broadcasted to all registered frameworks in the cluster whenever a slave is lost.
> This is unnecessary and kind of breaks the Mesos abstraction: Frameworks are a given a slice of the cluster, not the entirety. They know about the slice when offers are extended to them, so we shouldn't inform all of them when all agents go away.
> This message should instead be narrowcasted to all frameworks who have a stake in this agent: running tasks, pending offers, reservations, persistent volumes, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)