[
https://issues.apache.org/jira/browse/MESOS-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275029#comment-15275029
]
Anindya Sinha edited comment on MESOS-5143 at 6/9/16 1:31 AM:
--------------------------------------------------------------
RR published:
https://reviews.apache.org/r/48453/
https://reviews.apache.org/r/47082/
was (Author: anindya.sinha):
RR published:
https://reviews.apache.org/r/47082/
> 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)
