Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.1.9
-
None
Description
When mysqlmon detects that a server has been promoted, it first assigns the Master, Slave, Running status. On the next monitoring interval, it assigns the proper Master, Running status. This causes the new_master event to be triggered twice.
Here is an excerpt from a log file showing the behavior.
2017-10-24 19:49:29 notice : Server changed state: server2[192.168.121.202:3306]: new_master. [Slave, Running] -> [Master, Slave, Running]
|
2017-10-24 19:49:29 notice : [mysqlmon] A Master Server is now available: 192.168.121.202:3306
|
2017-10-24 19:49:30 notice : Server changed state: server2[192.168.121.202:3306]: new_master. [Master, Slave, Running] -> [Master, Running]
|
2017-10-24 19:49:30 notice : [mysqlmon] A Master Server is now available: 192.168.121.202:3306
|