[MESOS-1869] UpdateFramework message might reach the slave before Reregistered message and get dropped

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Sprint: Twitter Q4 Sprint 1
• Story Points: 1
• Assignee: Benjamin Mahler
• Reporter: Vinod Kone
• Shepherd: Vinod Kone
• Created: 06/Oct/14 17:37
• Updated: 09/Oct/14 01:32
• Resolved: 09/Oct/14 01:32

Description

In reregisterSlave() we send 'SlaveReregisteredMessage' before we link the slave pid, which means a temporary socket will be created and used.

Subsequently, after linking, we send the UpdateFrameworkMessage, which creates and uses a persistent socket.

This might lead to out-of-order delivery, resulting in UpdateFrameworkMessage reaching the slave before the SlaveReregisteredMessage and getting dropped because the slave is not yet (re-)registered.