Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.2.1
-
None
Description
When the mariadbmon is configured with ignore_external_masters, the monitor triggers a new_master event when the Slave of External Server status gets removed. This also happens when a slave is promoted as a master and the slave status is remove. These events should not happen as they are not truly functional changes in state.
2018-02-02 23:19:14 notice : Server changed state: server3[127.0.0.1:3002]: new_master. [Slave, Running] -> [Master, Slave, Running]
|
2018-02-02 23:19:14 notice : [mariadbmon] A Master Server is now available: 127.0.0.1:3002
|
2018-02-02 23:19:16 notice : Server changed state: server3[127.0.0.1:3002]: new_master. [Master, Slave, Running] -> [Master, Running]
|
2018-02-02 23:19:16 notice : [mariadbmon] A Master Server is now available: 127.0.0.1:3002
|