So I currently have an architecture where we have one master and one slave and read/write splitting in Maxscale. When we fail the slave, Maxscale correctly recognizes it and displays the information accordingly (and does not bring our website down), as well as allow both read and writes on the master. However, when we fail the master, mysqlfailover promotes the slave to the master, but Maxscale does not recognize that the slave is now the master. It does not seem to be granting it write permissions (which causes our website to go down).

When we fail either of the two databases, MySQL recognizes that there has been a change in our topology, but Maxscale does not.

What Maxscale configuration would allow us to correctly have Maxscale recognize this new topology (Slave is now the new master)? Is there an option that we have to select in order to have Maxscale correctly give the proper read/write permissions to the new master?

Since our topology is quite simple, I feel that Maxscale should be smart enough to realize that the new slave is now the master, and adjust accordingly

  • I've evaluated using MaxScale for my company's 3 node galera cluster and there are still some major things that need to be implemented or improved before we'll consider using it. Among them is manual and auto failover of nodes which somewhat works but is unusable in a real situation. I talked to one of their sales reps and they know about the issues but I don't know where they are on their priorities.
    – G-Nugget
    Commented Feb 29, 2016 at 16:57
  • No write perm? Due to lack of GRANTs? Or readonly?
    – Rick James
    Commented Mar 4, 2016 at 0:14
  • @G-Nugget - perhaps you want to start your own thread? And include things like whether you are writing to all 3 nodes, or pretending it is Master plus 2 slaves.
    – Rick James
    Commented Mar 4, 2016 at 0:16

1 Answer 1


Turns out the issue was that mysqlfailover was causing a conflict with maxscale. When the master would fail, mysqlfailover would automatically promote a new slave to master. However, when we did this it would cause a conflict with Maxscale (since it usually does it on its own), so it would lose track of which servers were the master and which were the slaves.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.