MySQL Router Doesn't Connect To The Primary Instance As The Metadata Server On Single-Primary InnoDB Cluster
(Doc ID 2983254.1)
Last updated on NOVEMBER 23, 2023
Applies to:
MySQL Router - Version 8.0 to 8.0 [Release 8.0]Information in this document applies to any platform.
Symptoms
When using MySQL Router on a single-primary InnoDB Cluster, MySQL Router should connect to the primary instance, because it checks-in upon 1 out of 10 TTLs. A check-in is an activity to register a router instance to InnoDB Cluster, and modifies table data. So, the metadata server must be writable.
However, MySQL Router can happen to connect to one of the secondaries on MySQL 8.0.32 or older. You can confirm connections from routers using SHOW PROCESSLIST command by checking the account user names, as described in <Document 2497041.1>.
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 |
| Cause |
| Solution |
| References |