[MESOS-1879] Handle a temporary one-way slave --> master socket closure.

• Type: Bug
• Status: Accepted
• Priority: Minor
• Resolution: Unresolved
• Component/s: agent
• Assignee: Unassigned
• Reporter: Benjamin Mahler
• Created: 08/Oct/14 21:45
• Updated: 12/Mar/16 23:02

Description

In the same spirit as MESOS-1668, we want to correctly handle a scenario where the slave --> master socket closes, and a new socket can be immediately re-established.

If this occurs, the ping / pongs will resume but there may be dropped messages sent by the slave, and so a re-registration would be a good safety net.

Issue Links

• relates to: MESOS-1529 Handle a network partition between Master and Slave
• relates to: MESOS-1668 Handle a temporary one-way master --> slave socket closure.
• relates to: MESOS-1963 Slave should use exited() to detect disconnection with Master.