Details
-
New Feature
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
25.10.0
-
None
-
None
Description
We have been debug a issue with customer, where during the master switch with transaction_reply enable, the customer keep facing application error cause implicit transaction ( autocommit =on), try to run a INSERT, and this insert fail, cause the master become in read-only.
The read-only indeed is part of the switch process, what we would have expected is that the explicit transaction, got hold by maxscale, until the new master is promoted and then fire the INSERT there, or at least untile the transaction_reply timeout is not reached.