Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
2.5.19
-
None
-
MXS-SPRINT-192, MXS-SPRINT-193
Description
Master status changes when runs stop slave on backend server.
2023-02-16 09:40:50 notice : Server changed state: server1[192.168.254.52:3306]: master_down. [Master, Running] -> [Down] |
2023-02-16 09:40:50 notice : Server changed state: server2[192.168.254.53:3306]: lost_slave. [Slave, Running] -> [Running]: Host: [192.168.254.52]:3306, IO Running: Yes, SQL Running: No |
2023-02-16 09:40:50 warning: [mariadbmon] Master has failed, but failover is disabled because monitor does not have exclusive locks on a majority of servers. |
2023-02-16 09:40:51 warning: [mariadbmon] The current master server 'server1' is no longer valid because it's not marked as master by the primary MaxScale, but there is no valid alternative to swap to. |
2023-02-16 09:40:51 notice : Server changed state: server1[192.168.254.52:3306]: master_up. [Down] -> [Master, Running] |
- topology
- 2 maxscale + 2 backend server
Attachments
Issue Links
- relates to
-
-
- Closed
-