[MXS-1965] Setting master into read-only mode causes all slaves to be lost Created: 2018-07-07  Updated: 2019-06-18  Resolved: 2019-06-18

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.3
Fix Version/s: 2.3.8

Type: Bug Priority: Major
Reporter: markus makela Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None


 Description   

Setting the master into read-only mode causes all servers to go into Running state. This causes at least the mxs1643_extra_events test to fail, possibly also mxs359_read_only.

2018-07-07 08:22:23   warning: [mariadbmon] The previous master server 'server1' is no longer a valid master because it is in read-only mode. Selecting new master.
2018-07-07 08:22:23   warning: [mariadbmon] 'server1' is not a valid master candidate because it is in read_only mode.
2018-07-07 08:22:23   warning: [mariadbmon] No valid master servers found.
2018-07-07 08:22:23   error  : [mariadbmon] No Master can be determined
2018-07-07 08:22:23   notice : Server changed state: server1[192.168.121.17:3306]: lost_master. [Master, Running] -> [Running]
2018-07-07 08:22:23   notice : Server changed state: server2[192.168.121.246:3306]: lost_slave. [Slave, Running] -> [Running]
2018-07-07 08:22:23   notice : Server changed state: server3[192.168.121.99:3306]: lost_slave. [Slave, Running] -> [Running]
2018-07-07 08:22:23   notice : Server changed state: server4[192.168.121.197:3306]: lost_slave. [Slave, Running] -> [Running]



 Comments   
Comment by markus makela [ 2019-06-18 ]

Tested with 2.3.8 and it seems to work now.

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