Installing and Configuring InnoDB Cluster _ by All database Solutions _ Medium

04/07/2024, 14:44 Installing and Configuring InnoDB Cluster | by All database Solutions | Medium
Installing and Configuring

InnoDB Cluster
All database Solutions · Follow
12 min read · Mar 17, 2022
Installing and Configuring InnoDB Cluster
Now a days HA(High Availability) and DR(Disaster Recovery)

Solutions are mandatory and required for mission critical
databases. In MySQL world , HA solution are provided using the
InnoDB or NDB Clustering Solution.
In this blog , We will discuss about the Installation and

Configuration of the InnoDB Cluster.
Installation Standards and Prerequisites
https://medium.com/@alldatabase.solutions/installing-and-configuring-innodb-cluster-e427250ac82c 1/30
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.
AdminAPI provides the dba.checkInstanceConfiguration()
method to verify that an instance meets the Group
Replication requirements, and the
dba.configureLocalInstance() method to configure an
instance to meet the requirements
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
Innodb before 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.
On Unix Python must be found as part of the shell

environment. To check that your system has Python
configured correctly issue following command :
$/usr/bin/env python
If a Python interpreter starts ,no further action is required.

And if previous command failed ,create soft link between
/usr/bin/python and your chosen Python binay.
Downloading and installing following components:

1) MySQL Server
2) MySQL Shell
3) MySQL Router
Installation
1) Install MySQL Server on all three node of the cluster.
2) Install MySQL Shell on all three node of the cluster.
apt-get install mysql-shell
3) Install MySQL Router on Application servers and DB server(if

needed).
4) Create cluster administration user on all three node of the

Cluster.
create user ‘clusteradmin’@’%’ identified by ‘********’;

grant all privileges on *.* to ‘clusteradmin’@’%’ with grant option;
GRANT SELECT ON mysql_innodb_cluster_metadata.* TO

clusteradmin@’%’;
GRANT SELECT ON performance_schema.global_status TO
GRANT SELECT ON
performance_schema.replication_applier_configuration TO
GRANT SELECT ON
performance_schema.replication_applier_status TO
GRANT SELECT ON
performance_schema.replication_applier_status_by_coordinator
TO clusteradmin@’%’;
GRANT SELECT ON
performance_schema.replication_applier_status_by_worker TO
GRANT SELECT ON
performance_schema.replication_connection_configuration TO
GRANT SELECT ON
performance_schema.replication_connection_status TO
GRANT SELECT ON
performance_schema.replication_group_member_stats TO
GRANT SELECT ON
performance_schema.replication_group_members TO
GRANT SELECT ON performance_schema.threads TO
clusteradmin@’%’ WITH GRANT OPTION;
5)Check and verify instance configuration.
mysqlsh — log-level=DEBUG3
mysql-js> dba.verbose=2
dba.checkInstanceConfiguration(‘mysqlhost01@mysqlhost01–
1:3306’)
root@mysqlhost01:~# hostname
mysqlhost01
root@mysqlhost01:~# mysqlsh — log-level=DEBUG3

MySQL Shell 8.0.17
Copyright © 2016, 2019, Oracle and/or its affiliates. All rights

reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates.
Other names may be trademarks of their respective owners.
Type ‘\help’ or ‘\?’ for help; ‘\quit’ to exit.

MySQL JS > dba.verbose=2
2
MySQL JS >
dba.checkInstanceConfiguration(‘clusteradmin@mysqlhost01:33
06’)
Please provide the password for
‘clusteradmin@mysqlhost01:3306’: ************************
Save password for ‘clusteradmin@mysqlhost01:3306’?
[Y]es/[N]o/Ne[v]er (default No):
Validating local MySQL instance listening at port 3306 for use in
an InnoDB cluster…
This instance reports its own address as mysqlhost01:3306

Clients and other cluster members will communicate with it
through this address by default. If this is not correct, the
report_host MySQL system variable should be changed.
Checking whether existing tables comply with Group Replication

requirements…
No incompatible tables detected
Checking instance configuration…
NOTE: Some configuration options need to be fixed:

+ — — — — — — — — — — — — — — — -+ — — — — — — — — — + —
— — — — — — — -+ — — — — — — — — — — — — — — — — — — —
——————+
| Variable | Current Value | Required Value | Note |
+ — — — — — — — — — — — — — — — -+ — — — — — — — — — + —
— — — — — — — -+ — — — — — — — — — — — — — — — — — — —
——————+
| binlog_checksum | CRC32 | NONE | Update the server variable |
| enforce_gtid_consistency | OFF | ON | Update read-only variable
and restart the server |
| gtid_mode | OFF | ON | Update read-only variable and restart the
server |
| server_id | 1 | <unique ID> | Update read-only variable and
restart the server |
+ — — — — — — — — — — — — — — — -+ — — — — — — — — — + —
— — — — — — — -+ — — — — — — — — — — — — — — — — — — —
——————+
Some variables need to be changed, but cannot be done

dynamically on the server.
NOTE: Please use the dba.configureInstance() command to
repair these issues.
{
“config_errors”: [
{
“action”: “server_update”,
“current”: “CRC32”,
“option”: “binlog_checksum”,
“required”: “NONE”
},
{
“action”: “server_update+restart”,
“current”: “OFF”,
“option”: “enforce_gtid_consistency”,
“required”: “ON”
},
{
“current”: “OFF”,
“option”: “gtid_mode”,
“required”: “ON”
},
{
“current”: “1”,
“option”: “server_id”,
“required”: “<unique ID>”
}
],
“status”: “error”
}
MySQL JS >
Follow the above steps on three node of the cluster.
4) Configure all three node of the cluster.
mysqlsh — log-level=DEBUG3
mysql-js> dba.verbose=2
dba.configureLocalInstance(‘clusteradmin@mysqlhost01:3306’)
MySQL JS >
dba.configureLocalInstance(‘clusteradmin@mysqlhost01:3306’)
Configuring local MySQL instance listening at port 3306 for use
in an InnoDB cluster…

NOTE: Some configuration options need to be fixed:

+ — — — — — — — — — — — — — + — — — — — — — -+ — — — — —
———+————————————————————————
—+
| Variable | Current Value | Required Value | Note |
+ — — — — — — — — — — — — — + — — — — — — — -+ — — — — —
———+————————————————————————
—+
| binlog_checksum | CRC32 | NONE | Update the server variable |
| enforce_gtid_consistency | OFF | ON | Update read-only variable
and restart the server |
| gtid_mode | OFF | ON | Update read-only variable and restart the
server |
| server_id | 1 | <unique ID> | Update read-only variable and
restart the server |
+ — — — — — — — — — — — — — + — — — — — — — -+ — — — — —
———+————————————————————————
—+
Some variables need to be changed, but cannot be done

dynamically on the server.
Do you want to perform the required configuration changes?

[y/n]: y
Do you want to restart the instance after configuring it? [y/n]: y
Configuring instance…
The instance ‘mysqlhost01:3306’ was configured for InnoDB
cluster usage.
Restarting MySQL…
NOTE: MySQL server at mysqlhost01:3306 was restarted.
Verify configuration again.
MySQL JS >
dba.checkInstanceConfiguration(‘clusteradmin@mysqlhost01:33
06’)
Validating local MySQL instance listening at port 3306 for use in
an InnoDB cluster…

Checking whether existing tables comply with Group Replication

requirements…
No incompatible tables detected
Checking instance configuration…

Instance configuration is compatible with InnoDB cluster
The instance ‘mysqlhost01:3306’ is valid for InnoDB cluster

usage.
{
“status”: “ok”
}
MySQL JS >
Similarly, Configure all other MySQL nodes.
5) Create Cluster
mysqlsh — uri clusteradmin@mysqlhost01:3306

var cluster = dba.createCluster(‘MysqlCluster’)
root@mysqlhost01:~# mysqlsh — uri

clusteradmin@mysqlhost01:3306

MySQL Shell 8.0.17

reserved.
affiliates.

Creating a session to ‘clusteradmin@mysqlhost01:3306’
Fetching schema names for autocompletion… Press ^C to stop.
Your MySQL connection id is 11
Server version: 8.0.17 MySQL Community Server — GPL
No default schema selected; type \use <schema> to set one.
MySQL mysqlhost01:3306 ssl JS >
MySQL mysqlhost01:3306 ssl JS > var cluster =
dba.createCluster(‘MysqlCluster’)
A new InnoDB cluster will be created on instance
‘mysqlhost01:3306’.
Validating instance at mysqlhost01:3306…
Instance configuration is suitable.

Creating InnoDB cluster ‘MysqlCluster’ on ‘mysqlhost01:3306’…
Adding Seed Instance…

Cluster successfully created. Use Cluster.addInstance() to add
MySQL instances.
At least 3 instances are needed for the cluster to be able to
withstand
Open in app
up to Sign up Sign in
one server failure.
Search Write
Cluster created, Please verify cluster using below commands :
var cluster = dba.getCluster()

cluster.status()
cluster.describe();
MySQL mysqlhost01:3306 ssl JS > var cluster = dba.getCluster()

MySQL mysqlhost01:3306 ssl JS > cluster.status()
{
“clusterName”: “MysqlCluster”,
“defaultReplicaSet”: {
“name”: “default”,
“primary”: “mysqlhost01:3306”,
“ssl”: “REQUIRED”,
“status”: “OK_NO_TOLERANCE”,
“statusText”: “Cluster is NOT tolerant to any failures.”,
“topology”: {
“mysqlhost01:3306”: {
“address”: “mysqlhost01:3306”,
“mode”: “R/W”,
“readReplicas”: {},
“role”: “HA”,
“status”: “ONLINE”,
“version”: “8.0.17”
}
},
“topologyMode”: “Single-Primary”
},
“groupInformationSourceMember”: “mysqlhost01:3306”
}
MySQL mysqlhost01:3306 ssl JS > cluster.describe();
{
“clusterName”: “MysqlCluster”,
“topology”: [
{
“label”: “mysqlhost01:3306”,
“version”: “8.0.17”
}
],
}
}
6) Add nodes to the cluster.
cluster.addInstance(‘clusteradmin@mysqlhost02:3306’);

cluster.addInstance(‘clusteradmin@mysqlhost02:3306’);
NOTE: The target instance ‘mysqlhost02:3306’ has not been pre-

provisioned (GTID set
is empty). The Shell is unable to decide whether incremental
distributed state
recovery can correctly provision it.
The safest and most convenient way to provision a new instance
is through
automatic clone provisioning, which will completely overwrite
the state of
‘mysqlhost02:3306’ with a physical snapshot from an existing
cluster member.
To use this method by default, set the ‘recoveryMethod’ option to

‘clone’.
The incremental distributed state recovery may be safely used if

you are sure
all updates ever executed in the cluster were done with GTIDs
enabled, there
are no purged transactions and the new instance contains the
same GTID set as
the cluster or a subset of it. To use this method by default, set the
‘recoveryMethod’ option to ‘incremental’.
Please select a recovery method [C]lone/[I]ncremental

recovery/[A]bort (default Clone):
Validating instance at mysqlhost02:3306…
Instance configuration is suitable.

A new instance will be added to the InnoDB cluster. Depending
on the amount of
data on the cluster this might take from a few seconds to several
hours.
Adding instance to the cluster…
WARNING: User ‘mysql_innodb_cluster_1397898975’@’%’ already

existed at instance ‘mysqlhost01:3306’. It will be deleted and
created again with a new password.
Monitoring recovery process of the new cluster member. Press
^C to stop monitoring and let it continue in background.
Clone based state recovery is now in progress.
NOTE: A server restart is expected to happen as part of the clone

process. If the
server does not support the RESTART command or does not
come back after a
while, you may need to manually start it back.
* Waiting for clone to finish…

NOTE: mysqlhost02:3306 is being cloned from mysqlhost01:3306
** Stage DROP DATA: Completed
** Clone Transfer
FILE COPY
#######################################################
##### 100% Completed
PAGE COPY
#######################################################
REDO COPY
#######################################################
** Stage RECOVERY: \
NOTE: mysqlhost02:3306 is shutting down…
* Waiting for server restart… ready

* mysqlhost02:3306 has restarted, waiting for clone to finish…
* Clone process has finished: 58.50 MB transferred in about 1
second (~inf TB/s)
Incremental distributed state recovery is now in progress.
* Waiting for distributed recovery to finish…

NOTE: ‘mysqlhost02:3306’ is being recovered from
‘mysqlhost01:3306’
* Distributed recovery has finished
The instance ‘mysqlhost02:3306’ was successfully added to the

cluster.
Similarly , Add other nodes to the cluster.
7) Configure MySQL Router on all the application and DB Servers

(if needed).
8) Check Cluster status post configuration.
MySQL mysqlhost02:3306 ssl JS > cluster.status()

{
“clusterName”: “MySQLCLUSTER”,
“primary”: “mysqlhost02:3306”,
“ssl”: “REQUIRED”,
“status”: “OK”,
“statusText”: “Cluster is ONLINE and can tolerate up to ONE
failure.”,
“topology”: {
“mode”: “R/O”,
“version”: “8.0.17”
},
“mode”: “R/W”,
“version”: “8.0.17”
},
“mode”: “R/O”,
“version”: “8.0.17”
}
},
},
“groupInformationSourceMember”: “mysqlhost02:3306”
}
9) Perform connectivity Test.

clusteradmin@localhost:6446
Please provide the password for ‘clusteradmin@localhost:6446’:
************************
Save password for ‘clusteradmin@localhost:6446’?
MySQL Shell 8.0.17

reserved.

affiliates.

Creating a session to ‘clusteradmin@localhost:6446’
MySQL localhost:6446 ssl JS > \sql
Switching to SQL mode… Commands end with ;
MySQL localhost:6446 ssl SQL > show databases;
+ — — — — — — — — — — — — — — — -+
| Database |
+ — — — — — — — — — — — — — — — -+
| information_schema |
| mysql |
| mysql_innodb_cluster_metadata |
| performance_schema |
| sys |
+ — — — — — — — — — — — — — — — -+
5 rows in set (0.0013 sec)
MySQL localhost:6446 ssl SQL > select @@port;
+————+
| @@port |
+————+
| 3306 |
+————+
1 row in set (0.0007 sec)
MySQL localhost:6446 ssl SQL > select @@hostname;
+———————+
| @@hostname |
+———————+
| mysqlhost01 |
+———————+
MySQL localhost:6446 ssl SQL >

clusteradmin@localhost:6446
Please provide the password for ‘clusteradmin@localhost:6446’:
************************
Save password for ‘clusteradmin@localhost:6446’?
MySQL Shell 8.0.17

reserved.
affiliates.

Creating a session to ‘clusteradmin@localhost:6446’
MySQL localhost:6446 ssl JS > \sql
Switching to SQL mode… Commands end with ;
MySQL localhost:6446 ssl SQL > show databases;
+ — — — — — — — — — — — — — — — -+
| Database |
+ — — — — — — — — — — — — — — — -+
| information_schema |
| mysql |
| mysql_innodb_cluster_metadata |
| performance_schema |
| sys |
+ — — — — — — — — — — — — — — — -+
5 rows in set (0.0011 sec)
MySQL localhost:6446 ssl SQL > select @@port;
+————+
| @@port |
+————+
| 3306 |
+————+
MySQL localhost:6446 ssl SQL > select @@hostname;
+———————+
| @@hostname |
+———————+
| mysqlhost01 |
+———————+
MySQL localhost:6446 ssl SQL >
========================================
You can also , Visit our Blogs for related topic on MySQL InnoDB
Cluster:
1)MySQL InnoDB Cluster node Addition Issue: —
Cluster.addInstance: : MySQL server has gone away
(RuntimeError)
2)Install & Configure MySQL Router — MySQL InnoDB Cluster
3)Restoring a Failed member in InnoDB Cluster
Database MySQL Mysql Workbench
Written by All database Solutions Follow
14 Followers
Professional DBA with exp in Oracle ,MySQL and MSSQL.
More from All database Solutions
All database Solutions All database Solutions
Oracle Standby/DR — Oracle Flashback Database ,

Changing the Data Guard… Restore point and…
Oracle Data Guard provides three Flashback Database is as name
modes to protect the data in the… suggest allow you to revert or rewind…
Dec 5, 2022 1 Oct 4, 2022 3
All database Solutions All database Solutions
Oracle Database Resource For Oracle DBA data

Manager (DBRM)-Exadata migration is common activit…
The Oracle Database Resource High Level Steps:
Manager allows
Dec 29, 2023 1 Jun 7, 2023
See all from All database Solutions
Recommended from Medium
Alexander Nguyen in Level Up Coding Sufyan Maan, M.Eng in ILLUMINATION
The resume that got a What Happens When You

software engineer a… Start Reading Every Day
1-page. Well-formatted. Think before you speak. Read before
you think. — Fran Lebowitz
Jun 1 10.8K 130 Mar 12 24K 511
Lists
data science and AI Natural Language

40 stories · 196 saves Processing
1561 stories · 1093 saves
Unbecoming Saurav Poudel
10 Seconds That Ended My Learning Spanish, Finalmente

20 Year Marriage And why it has been one
It’s August in Northern Virginia, hot transformative life experience.
and humid. I still haven’t showered…
Feb 16, 2022 83K 1127 Jun 20 2
Andrés Felipe Vidal LORY
ERROR 2002 (HY000): Can’t A basic question in security

connect to local MySQL… Interview: How do you store…
Encountering the “ERROR 2002 Explained in 3 mins.
(HY000): Can’t connect to local…
Feb 5 1 1 May 12 3.8K 39
See more recommendations

Installing and Configuring InnoDB Cluster _ by All database Solutions _ Medium

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installing and Configuring InnoDB Cluster _ by All database Solutions _ Medium

Uploaded by

Copyright:

Available Formats

04/07/2024, 14:44 Installing and Configuring InnoDB Cluster | by All database Solutions | Medium

Installing and Configuring

Installing and Configuring InnoDB Cluster

Now a days HA(High Availability) and DR(Disaster Recovery)

In this blog , We will discuss about the Installation and

Installation Standards and Prerequisites

Before installing a production deployment of InnoDB cluster,

InnoDB cluster uses Group Replication and therefore your

Group Replication members can contain tables using a

The Performance Schema must be enabled on any instance

The provisioning scripts that MySQL Shell uses to configure

On Unix Python must be found as part of the shell

If a Python interpreter starts ,no further action is required.

Downloading and installing following components:

2) Install MySQL Shell on all three node of the cluster.

apt-get install mysql-shell

3) Install MySQL Router on Application servers and DB server(if

4) Create cluster administration user on all three node of the

create user ‘clusteradmin’@’%’ identified by ‘********’;

GRANT SELECT ON mysql_innodb_cluster_metadata.* TO

5)Check and verify instance configuration.

root@mysqlhost01:~# mysqlsh — log-level=DEBUG3

Copyright © 2016, 2019, Oracle and/or its affiliates. All rights

Type ‘\help’ or ‘\?’ for help; ‘\quit’ to exit.

This instance reports its own address as mysqlhost01:3306

Checking whether existing tables comply with Group Replication

Checking instance configuration…

NOTE: Some configuration options need to be fixed:

Some variables need to be changed, but cannot be done

Follow the above steps on three node of the cluster.

4) Configure all three node of the cluster.

This instance reports its own address as mysqlhost01:3306

NOTE: Some configuration options need to be fixed:

Some variables need to be changed, but cannot be done

Do you want to perform the required configuration changes?

Verify configuration again.

This instance reports its own address as mysqlhost01:3306

Checking whether existing tables comply with Group Replication

Checking instance configuration…

The instance ‘mysqlhost01:3306’ is valid for InnoDB cluster

Similarly, Configure all other MySQL nodes.

mysqlsh — uri clusteradmin@mysqlhost01:3306

root@mysqlhost01:~# mysqlsh — uri

Save password for ‘clusteradmin@mysqlhost01:3306’?

Copyright © 2016, 2019, Oracle and/or its affiliates. All rights

Type ‘\help’ or ‘\?’ for help; ‘\quit’ to exit.

Validating instance at mysqlhost01:3306…

This instance reports its own address as mysqlhost01:3306

Instance configuration is suitable.

Adding Seed Instance…

Cluster created, Please verify cluster using below commands :

var cluster = dba.getCluster()

MySQL mysqlhost01:3306 ssl JS > var cluster = dba.getCluster()

6) Add nodes to the cluster.

MySQL mysqlhost01:3306 ssl JS >

NOTE: The target instance ‘mysqlhost02:3306’ has not been pre-

To use this method by default, set the ‘recoveryMethod’ option to

The incremental distributed state recovery may be safely used if

Please select a recovery method [C]lone/[I]ncremental

This instance reports its own address as mysqlhost02:3306

Instance configuration is suitable.

Adding instance to the cluster…

WARNING: User ‘mysql_innodb_cluster_1397898975’@’%’ already

NOTE: A server restart is expected to happen as part of the clone