[MXS-1147] add sticky_master option to MySQL Monitor Created: 2017-02-27  Updated: 2017-08-22  Resolved: 2017-08-22

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

Type: New Feature Priority: Minor
Reporter: sava Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS Linux release 7.3.1611
maxscale-2.0.1-2.x86_64


 Description   

There is three servers. I setup it with mariadb replication and maxscale R/W splitting router.

server2 -> server3 -> server1

The master is server2. The server3 is intermediate database. The server1 is a slave.
If the server2 was failed, writing queries failover to server3.
If the server2 came back, writing queries failback to server2.
And It will occur replication error on the server3.
I don't want this behavior.
I want option to fix the master node.

 Comments   
Comment by markus makela [ 2017-03-20 ]

The replication-manager might solve these problems.

Comment by markus makela [ 2017-08-22 ]

This is actually about intermediate master being used as real masters. With 2.1, MaxScale should not pick the intermediate master as a real master if replication is configured.

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