Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently the driver only calls disconnected() when it gets NoMasterDetected() message.
But during a master failover the driver typically only gets NewMasterDetected() and sets an internal variable 'connected = false'. Subsequent driver calls (launchTasks, killTask) are rejected by the driver until it re-registers with a master.
At Twitter, we have seen this window to be as large as ~5s. It would be nice to inform the scheduler that the driver is 'disconnected()' in this situation.