[MXS-4511] master status change when run stop slave Created: 2023-02-16  Updated: 2024-02-05  Resolved: 2023-11-06

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

Type: Bug Priority: Major
Reporter: Allen Lee (Inactive) Assignee: Esa Korhonen
Resolution: Incomplete Votes: 0
Labels: None

Attachments: Zip Archive bug-report.zip    
Issue Links:
Relates
relates to MXS-4508 Mariadbmon loses locks without report... Closed
Sprint: 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

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