Comments - Readwritesplit
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Is there a parameter to make maxscale send writes to a the new master when the master fails on write instead of failing on the client side? In trying to test this out with worst case scenarios I've been forcibly killing the master at the same moment I'm updating drupal. Maxscale does it's job and switches the master node to another node and if I reload the page it works but I'd love it instead of failing maxscale made the client pause until it connected to the new master and retry instead.
Right now master failover isn't supported in readwritesplit but it is possible to implement it with some code changes.
The main idea why readwritesplit closes the session when the master changes is to prevent "silent" master failover or replication topology changes. Sometimes this isn't what is wanted and being able to change masters transparently to the application is very valuable. Adding support for transparent master failover would be quite nice as it would integrate MaxScale better with software such as replication-manager.