Before installing a production deployment of InnoDB cluster, ensure that the server instances you intend to use meet the following requirements.
InnoDB cluster uses Group Replication and therefore your server instances must meet the same requirements. See Section 18.9.1, “Group Replication Requirements”. AdminAPI provides the
dba.checkInstanceConfiguration()method to verify that an instance meets the Group Replication requirements, and the
dba.configureInstance()method to configure an instance to meet the requirements.Note
When using a sandbox deployment the instances are configured to meet these requirements automatically.
Group Replication members can contain tables using a storage engine other than
InnoDB, for example
MyISAM. Such tables cannot be written to by Group Replication, and therefore when using InnoDB cluster. To be able to write to such tables with InnoDB cluster, convert all such tables to
InnoDBbefore using the instance in a InnoDB cluster.
The Performance Schema must be enabled on any instance which you want to use with InnoDB cluster.
The provisioning scripts that MySQL Shell uses to configure servers for use in InnoDB cluster require access to Python version 2.7. For a sandbox deployment Python is required on the single machine used for the deployment, production deployments require Python on each server instance which should run MySQL Shell locally, see Persisting Settings.
On Windows MySQL Shell includes Python and no user configuration is required. On Unix Python must be found as part of the shell environment. To check that your system has Python configured correctly issue:
$ /usr/bin/env python
If a Python interpreter starts, no further action is required. If the previous command fails, create a soft link between
/usr/bin/pythonand your chosen Python binary.
From version 8.0.17, instances must use a unique
server_idwithin a InnoDB cluster. When you use the
operation, if the
instanceis already used by an instance in the cluster then the operation fails with an error.