MySQL Router Connect_timeout for Unstable Network Environments ( not GR / IC )
(Doc ID 2562913.1)
Last updated on SEPTEMBER 07, 2022
Applies to:
MySQL Router - Version 8.0 and laterInformation in this document applies to any platform.
Router is not designed to work "out-of-the-box" with the existing mature , yet simple Source-Replica replication environments.
This is due to the nature of how the replication works with respect to moving their roles based on network status ( this needs to be controlled via 3rd party scripts ).
It should then be clear to see how this can lead to inconsistencies in the typical Source-Replica or even a Source-Source ( Active-Passive ) environment with Router ( without sufficient external intervention )
Symptoms
The app / MySQL error log is showing duplicate row errors and replication is out of sync.
Only Group Replication / InnoDB Cluster has the inbuilt controls to prevent writes to non primary node(s).
Changes
No obvious or immediate changes.
Very likely an intermittent unstable network issue.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |