Search Results
https://dev.mysql.com/doc/mysql-shell/9.4/en/configuring-automatic-rejoin-of-instances.html
If exitStateAction is set to OFFLINE_MODE, instances which leave the cluster unexpectedly become read-only and also enter offline mode, where they disconnect existing clients and do not accept new connections (except from clients with administrator ... Instances running MySQL 8.0.16 and later support the Group Replication automatic rejoin functionality, which enables you to configure instances to automatically rejoin the cluster after being ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/innodb-clusterset-gtid-repair.html
If the primary cluster remains online after the failover, it could continue to accept transactions from clients through any MySQL Router instances that are still connected to it, and pass these to any replica clusters that are still connected to it.
https://dev.mysql.com/doc/mysql-shell/9.4/en/innodb-clusterset-requirements.html
The server can connect to the primary cluster in the InnoDB ClusterSet, and the primary cluster can connect to it. The basis of an InnoDB ClusterSet deployment is an existing InnoDB Cluster at MySQL 8.0.27 or higher, and a number of standalone ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/innodb-clusterset-router-setroutingoption.html
none: (Default) All current connections are disconnected and new connections are refused. This option has no effect if group_replication_unreachable_majority_timeout is set to a positive value and group_replication_exit_state_action is either ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-innodb-cluster-from-group-replication.html
To adopt an existing Group Replication group, connect to a group member using MySQL Shell. We connect to gr-member-2, a secondary instance, while gr-member-1 is functioning as the group's primary. If you have an existing deployment of Group ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-innodb-cluster-upgrade.html
All the existing user connections are maintained, and any new connections are routed according to the cached metadata. Much of the process of upgrading an InnoDB Cluster consists of upgrading the instances in the same way as documented at Upgrading ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-innodb-replicaset.html
You can use InnoDB ReplicaSet over a Wide Area Network (WAN) with no impact on write performance, as the server instances are connected by asynchronous replication channels and do not need consensus on transactions. Although there is no limit to the ... The AdminAPI includes support for InnoDB ReplicaSet, which enables you to administer a set of MySQL instances similarly running asynchronous GTID-based replication, which is completely transaction-based, to InnoDB ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-shell-reporting-builtin-threads.html
The built-in MySQL Shell report threads lists the current threads in the connected MySQL server which belong to the user account that is used to run the report. The report works with servers running all supported MySQL 5.7, 8.0, and 8.1 versions.
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-shell-utilities-json-import-command.html
The syntax is as follows: mysqlsh user@host:port/mydb --import <path> [target] [tableColumn] [options] As with the mysqlsh command interface, you must specify the target database, either in the URI-like connection string, or using an additional ...
https://dev.mysql.com/doc/mysql-shell/9.4/en/mysql-shell-utilities.html
collectDiagnostics() A diagnostics generation utility that gathers information from the connected MySQL server, generates reports in TSV and YAML formats, and presents them in a zip archive in the location of your choice. As a result, if you connect ...To access the utilities from within MySQL Shell, use the util global object, which is available in JavaScript and Python modes, but not SQL ...