8.10 Dissolving a ClusterSet

This section describes how to dissolve a ClusterSet using ClusterSet.dissolve().

Note

All user data is retained.

ClusterSets are dissolved in the following way:

Replication accounts are dropped from all contactable members.
The metadata schema is dropped from all contactable members.
The asynchronous replication channel is stopped on all contactable members.
Each individual Cluster is dissolved.

If any instance is unreachable, the operation fails, generating an error. To ignore unreachable instances and dissolve the ClusterSet, use the force option. You can also use this option if a timeout is reached waiting for all transactions to be applied on a secondary member.

ClusterSet.dissolve() accepts a timeout option, which specifies the number of seconds to wait for pending transactions to be applied in each contactable instance of the ClusterSet. The default value is retrieved from the dba.gtidWaitTimeout option.

This command can also be run with the dryRun option set to true. This tests all settings without making any changes.