Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.3
-
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]
|