Comments - MaxScale redirects writes in slave
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.
This must be a bug in the MaxScale query parsing that causes the query to be classified as a read. What version of MaxScale are you using?
Hello Markus, I'm using maxscale 6.4.1.
Meanwhile, I have solved the issue by adding a hintfilter and suffixing all UPDATE/DELETE/REPLACE/INSERT queries with '/* maxscale route to master */'. A month has passed and the slave is in perfect sync with its master and no more replication issues.
I opened MXS-4269 for this bug.
Awesome, thanks.