Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
None
-
None
-
2017-43, 2017-44
Description
It seems that detecting that a master is down is not quite as straightforward as one could imagine. The RM apparently does not immediately conclude that a master that appears to be down actually is down, but makes various attempts before finally accepting that it indeed is down. That apparently is necessary in order to ensure that unnecessary promotions are not performed.
Attachments
Issue Links
- blocks
-
MXS-1438 Enhance the master down detection logic of MySQL Monitor based upon the findings of MXS-1436
- Closed