Search



Search Results
Displaying 1861 to 1870 of 1965 total results
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-failover.html
When you issue the clusterSet.forcePrimaryCluster() command, MySQL Shell checks that the target replica cluster complies with the requirements to take over as the primary cluster, and returns an error if it does not. An emergency failover makes a ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-gtid-repair.html
AdminAPI's clusterSet.status() command warns you if an InnoDB Cluster's GTID set is inconsistent with the GTID set on the primary cluster in the InnoDB ClusterSet. A cluster in this state has extra transactions compared to the other clusters in the ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-rejoin.html
When you issue the clusterSet.rejoinCluster() command, MySQL Shell checks that the target cluster meets the requirements to rejoin the ClusterSet, and returns an error if it does not. If an InnoDB Cluster is part of an InnoDB ClusterSet deployment, ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-remove.html
If any of these conditions are not met, an error is returned. To remove a cluster from the InnoDB ClusterSet, use clusterSet.removeCluster() command. A force option is available if the cluster cannot be contacted at all. clusterSet.removeCluster() ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-requirements.html
cluster.setupAdminAccount() is not available on a standalone instance, and if you create one of those accounts on the standalone instances using dba.configureInstance or manually, it will subsequently be replicated from the primary cluster, causing ... The basis of an InnoDB ClusterSet deployment is an existing InnoDB Cluster at MySQL 8.0.27 or higher, and a number of standalone MySQL Server instances that can be formed into replica clusters to provide disaster tolerance for this primary ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-switchover.html
When you issue the clusterSet.setPrimaryCluster() command, MySQL Shell checks that the target replica cluster complies with the requirements to take over as the primary cluster, and returns an error if it does not. A controlled switchover makes a ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/innodb-clusterset-user-accounts.html
If the accounts already exist on a server in the replica cluster, this causes a replication error, and the server cannot join the cluster. The member servers in an InnoDB Cluster make use of three types of user accounts. One InnoDB Cluster server ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/manage-sandbox-instances.html
The operation fails with a timeout, and the error log contains: 2020-03-26T11:43:12.969131Z 5 [System] [MY-013381] [Server] Server upgrade from '80019' to '80020' started. Once a sandbox instance is running, it is possible to change its status at ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/mysql-adminapi-reset-replication-account-credentials.html
Whether the operation should continue in the event of an error, such as an instance is OFFLINE and the reset cannot be performed. reset_replication_accounts_password() enables you to reset, or recreate, the credentials for the internal recovery and ...
https://dev.mysql.com/doc/mysql-shell/9.7/en/mysql-innodb-cluster-upgrade-rolling.html
Use dba.configureInstance() to fix it." ], "memberId": "247131ab-8926-11ec-850b-02001707f44a", "memberRole": "PRIMARY", "memberState": "ONLINE", "mode": "R/W", "readReplicas": {}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": ... To upgrade the server instances in an InnoDB Cluster, complete the following steps: Upgrade MySQL ...
Displaying 1861 to 1870 of 1965 total results