[MESOS-1811] Reconcile disconnected/deactivated semantics in the master code

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Target Version/s: 0.21.0
• Epic Link: Reconciliation
• Sprint: Mesos Q3 Sprint 5, Mesos Q3 Sprint 6
• Story Points: 3
• Assignee: Vinod Kone
• Reporter: Vinod Kone
• Shepherd: Benjamin Mahler
• Created: 18/Sep/14 01:20
• Updated: 25/Sep/14 20:55
• Resolved: 25/Sep/14 20:55

Description

Currently the master code treats a deactivated and disconnected slave similarly, by setting 'disconnected' variable in the slave struct. This causes us to disconnect() a slave in cases where we really only want to deactivate() the slave (e.g., authentication).

It would be nice to differentiate these semantics by adding a new variable "active" in the Slave struct.

We might want to do the same with the Framework struct for consistency.

Issue Links

• blocks: MESOS-1668 Handle a temporary one-way master --> slave socket closure.