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 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 an InnoDB Cluster.
There must be no inbound replication channels on any server instance when you set up the cluster. The channels created automatically by Group Replication (
group_replication_recovery) are allowed on a replication group that is being adopted. InnoDB Cluster does not support manually configured asynchronous replication channels outside of those that are managed using AdminAPI. If you are migrating an existing replication topology to an InnoDB Cluster deployment and need to skip this validation temporarily during the setup process, you can use the
forceoption when you create the cluster to bypass it.
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. 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. For more information, see Supported Languages.
From version 8.0.17, instances must use a unique
server_idwithin an 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.
From version 8.0.23, instances should be configured to use the parallel replication applier. See Configuring the Parallel Replication Applier.
During the process of configuring an instance for InnoDB Cluster, the majority of the system variables required for using an instance are configured. But AdminAPI does not configure the
transaction_isolationsystem variable, which means that it defaults to
REPEATABLE READ. This does not impact a single-primary cluster, but if you are using a multi-primary cluster then unless you rely on
REPEATABLE READsemantics in your applications, we recommend using the
READ COMMITTEDisolation level. See Group Replication Limitations.
The relevant configuration options for the instance, particularly the Group Replication configuration options, must be in a single option file. InnoDB Cluster only supports a single option file for server instances and does not support the use of the
--defaults-extra-fileoption to specify an additional option file. For any AdminAPI operation working with the instance's option file the main file must be specified. If you want to use multiple option files for configuration options that do not relate to InnoDB Cluster, you must configure the files manually, make sure they are updated correctly considering the precedence rules for the use of multiple option files, and ensure that the settings relating to InnoDB Cluster are not incorrectly overwritten by options in an extra unrecognized option file.