Bug #108373 | ability to remove an instance from all cluster metadata but keep GTID | ||
---|---|---|---|
Submitted: | 2 Sep 2022 19:30 | Modified: | 10 Jun 2024 10:18 |
Reporter: | Jay Janssen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Shell AdminAPI InnoDB Cluster / ReplicaSet | Severity: | S4 (Feature request) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Sep 2022 19:30]
Jay Janssen
[2 Sep 2022 19:40]
Jay Janssen
Maybe to put it another way: I want a big red button to convert an instance that is a cluster/clusterset member back to a standalone instance again.
[5 Sep 2022 5:51]
MySQL Verification Team
Hello Jay Janssen, Thank you for the feature request! regards, Umesh
[10 Jun 2024 10:18]
Edward Gilmore
Posted by developer: Added the following note to the MySQL Shell 9.0.0 release notes: It is now possible to dissolve a ClusterSet, partially or completely, using the following methods: clusterSet.dissolve(): dissolves the ClusterSet completely by stopping replication between each replica and primary Cluster and removing any metadata related to the ClusterSet. Each cluster of the ClusterSet is also dissolved. The dissolve option of clusterSet.removeCluster(): removes the specified Cluster from the ClusterSet, enabling it to function as a standalone Cluster. Thank you for the bug report.