The MySQL server is running with the --read-only
Setup:
3 node MySQL 5.7.21 Innodb cluster community Edition, single primary.
MySQL Router: 2.1.4
We have been facing scenarios where in application pools 20 connections onto the cluster.
No when the primary switched over to a different node (due to network fluctuations) and the old primary is secondary now.
Now the connections which were established on the primary earlier do not move to the new primary or get killed/terminated. The application throws the below error as the node is a secondary.
Caused by: java.sql.BatchUpdateException: The MySQL server is running with the
--read-only option so it cannot execute this statement
Is this something MySQLRouter/Innodb cluster needs to handle ?
or any configuration to be take care off or any feature ?
Subject
Views
Written By
Posted
The MySQL server is running with the --read-only
6302
May 14, 2019 05:24AM
869
June 21, 2019 02:19AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.