[MXS-685] 1.4.1: ReadWrite Split on Master-Master setup doesn't chose master, logs "RUNNING MASTER" error message instead (related to MXS-511?) Created: 2016-04-24  Updated: 2016-05-18  Resolved: 2016-05-18

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 1.4.1
Fix Version/s: 2.0.0

Type: Bug Priority: Major
Reporter: Stefan Rubner Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: mmmon
Environment:

Debian Wheezy, MariaDB 10.0.19 Master-Master-Replication


 Description   

When moving a client's setup from MMM script based setup to MaxScale I ran into the same problem that is described in MXS-511 with the difference that this setup isn't a Galera cluster but a master-master replication. So the obvious difference is that the monitor plugin used is 'mmmon'.
I verified that both nodes are indeed synced.

Configs and logs can be provided if needed.

 Comments   
Comment by markus makela [ 2016-05-18 ]

There was a small window where the state was modified to a bad state and to a correct state right after it.

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