[MXS-1643] Too many monitor events are triggered Created: 2018-02-02  Updated: 2018-06-27  Resolved: 2018-02-12

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.2.1
Fix Version/s: 2.2.2

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: 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



 Comments   
Comment by markus makela [ 2018-02-12 ]

The server states are now handled correctly so that the extra new_master event is not triggered.

Generated at Thu Feb 08 04:08:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.