[MESOS-5143] LostSlaveMessage should not be broadcasted.

• Type: Bug
• Status: Reviewable
• Priority: Major
• Resolution: Unresolved
• Component/s: master
• Assignee: Anindya Sinha
• Reporter: Yan Xu
• Shepherd: Yan Xu
• Created: 07/Apr/16 20:57
• Updated: 09/Jun/16 01:31

Description

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.