Bug #95010 | custer.setOption("clusterName","myNewClusterName") breaks InnoDb Cluster | ||
---|---|---|---|
Submitted: | 12 Apr 2019 15:41 | Modified: | 9 Feb 2023 10:58 |
Reporter: | Truphone DBA | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Router | Severity: | S2 (Serious) |
Version: | 8.0.15 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[12 Apr 2019 15:41]
Truphone DBA
[12 Apr 2019 15:48]
Truphone DBA
The bug https://bugs.mysql.com/bug.php?id=94057 covers some of this use case, but not all. Does not make sense that a cluster rename involving a router bootstraping and restart in order to work.
[9 Feb 2023 10:58]
Edward Gilmore
Posted by developer: Added the following note to the MySQL Router 8.0.33 release notes: Renaming a cluster, using cluster.setOption(), caused routing to fail due to an issue with MySQL Router configuration. This issue was caused by MySQL Router using the cluster name written to the MySQL Router configuration file during bootstrapping. The cluster name was then used in queries to the metadata cache, which failed when the cluster was renamed. As of this release, the cluster name is not used, the UUID is used instead. That is, Group Replication UUID for group replication clusters, ClusterSet UUID for ClusterSets, and Cluster UUID for ReplicaSet clusters. The UUID is written to MySQL Router's JSON state file. Note For backward compatibility, the cluster name is still written to the configuration file and will be used if UUIDs are not available.