[MESOS-786] Update semantics of when framework registered()/reregistered() get called

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Epic Link: Scheduler API v1
• Sprint: Twitter Mesos Q2 Sprint 6, Twitter Mesos Q3 Sprint 1
• Story Points: 3
• Assignee: Vinod Kone
• Reporter: Vinod Kone
• Created: 30/Oct/13 19:39
• Updated: 05/Oct/16 20:58
• Resolved: 07/Jul/15 19:35

Description

Current semantics:

1) Framework connects w/ master very first time --> registered()
2) Framework reconnects w/ same master after a zk blip --> reregistered()
3) Framework reconnects w/ failed over master --> registered()
4) Failed over framework connects w/ same master --> registered()
5) Failed over framework connects w/ failed over master --> registered()

Updated semantics:

Everything same except
3) Framework reconnects w/ failed over master --> reregistered()

Issue Links

• is related to: MESOS-6249 On Mesos master failover the reregistered callback is not triggered
• is related to: MESOS-2910 Add an Event message handler to scheduler driver
• is related to: MESOS-3088 Update scheduler driver to send SUBSCRIBE call