This document provides a comprehensive guide for deploying and managing MySQL architectures, specifically focusing on a hands-on tutorial by Frédéric Descamps. It includes step-by-step instructions for installing MySQL components, setting up instances, and configuring replication for high availability. The guide emphasizes practical labs where users can learn to execute commands for managing MySQL servers effectively.

1. Frédéric Descamps
Community Manager
MySQL
MySQL Architectures
Design the Right Solution for Your Needs

2. Before we start:
Ensure that you have:
a laptop (or a computer, or a cloud instance)
MySQL 8.0.29 installed on it
MySQL Shell 8.0.29 installed on it
MySQL Router 8.0.29 installed on it
Visual Studio Code and MySQL Shell extention [optional]
If not, now, it's the right time to do it before we start...
Copyright @ 2022 Oracle and/or its affiliates.
2

3. Frédéric Descamps
Community Manager
MySQL
MySQL Architectures
Design the Right Solution for Your Needs

4. Who am I ?
about.me/lefred
Copyright @ 2022 Oracle and/or its affiliates.
4

5. @lefred
MySQL Evangelist
using MySQL since version 3.20
devops believer
likes 🏀
living in
h ps://lefred.be
Frédéric Descamps
Copyright @ 2022 Oracle and/or its affiliates.
5

6. Housekeeping
some information
Copyright @ 2022 Oracle and/or its affiliates.
6

7. Housekeeping and FAQ
Slides will be available later today !
We will have 2 breaks
Don't fall behind, if you have a question or a problem do not hesitate to reach out to me!
When you see this image (look on the top right of this slide), it's your turn.
Yes, you need to do all labs, each lab builds on the previous lab
Prepare a sheet and a pen (or open your text editor) to write some notes, like credentials,
ports, ...
Copyright @ 2022 Oracle and/or its affiliates.
7

8. MySQL Shell is now included in Visual Studio Code:
Copyright @ 2022 Oracle and/or its affiliates.
8

9. Copyright @ 2022 Oracle and/or its affiliates.
9

10. Windows Users - Installation
For Microsoft Windows users, please use MySQL Installer to install the required products:
Copyright @ 2022 Oracle and/or its affiliates.
10

11. MySQL Architectures
the Agenda in Pictures
Copyright @ 2022 Oracle and/or its affiliates.
11

12. We will start with the deployment of a
single instance of MySQL.
MySQL architectures: Agenda
Copyright @ 2022 Oracle and/or its affiliates.
12

13. We will create a second instance and setup
Asynchronous replication.
We will also deploy MySQL Router.
MySQL architectures: Agenda
Copyright @ 2022 Oracle and/or its affiliates.
13

14. We will then upgrade to MySQL InnoDB
Cluster and add a third MySQL instance.
MySQL architectures: Agenda
Copyright @ 2022 Oracle and/or its affiliates.
14

15. MySQL architectures: Agenda
To nish with the ultimate High Availability and Disaster Recovery solution:
Copyright @ 2022 Oracle and/or its affiliates.
15

16. MySQL
Single Instance
Copyright @ 2022 Oracle and/or its affiliates.
16

17. You should have already downloaded and
installed MySQL and MySQL Shell on your
system.
During this tutorial, we will use MySQL Shell
sandbox capabilities to simulate multiple
servers.
Let's start the rst hands-on LAB !
MySQL Single Instance
Copyright @ 2022 Oracle and/or its affiliates.
17

18. LAB 1
Copyright @ 2022 Oracle and/or its affiliates.
18

19. LAB 1: deployment and connection to MySQL
You can use MySQL Shell or MySQL Shell for Visual Studio Code.
We need to rst launch MySQL Shell and deploy our rst sandbox.
This is the information we will use:
port: 3310
root password: MySQL123
We will use the dba.deploySandboxInstance() method:
JS> dba.deploySandboxInstance(3310, {password: 'MySQL123'})
Copyright @ 2022 Oracle and/or its affiliates.
19

20. LAB 1: deployment and connection to MySQL
Copyright @ 2022 Oracle and/or its affiliates.
20

21. LAB 1: deployment and connection to MySQL
Now we can connect to our sandbox MySQL instance:
JS> c root@localhost:3310
Copyright @ 2022 Oracle and/or its affiliates.
root / MySQL123
port: 3310
21

22. LAB 1: deployment and connection to MySQL
Now we can connect to our sandbox MySQL instance:
JS> c root@localhost:3310
Copyright @ 2022 Oracle and/or its affiliates.
root / MySQL123
port: 3310
21

23. LAB 1: deployment and connection to MySQL
Copyright @ 2022 Oracle and/or its affiliates.
root / MySQL123
port: 3310
22

24. LAB 1: inserting data
We will now create a new table and add data to it:
SQL> CREATE DATABASE perconalive;
SQL> u perconalive
SQL> CREATE TABLE t1 (id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
port INT);
SQL> INSERT into t1 (port) VALUES (@@port);
Copyright @ 2022 Oracle and/or its affiliates.
23

25. LAB 1: inserting data
We will now create a new table and add data to it:
SQL> CREATE DATABASE perconalive;
SQL> u perconalive
SQL> CREATE TABLE t1 (id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
timestamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
port INT);
SQL> INSERT into t1 (port) VALUES (@@port);
SQL> SELECT * FROM t1;
+----+---------------------+------+
| id | timestamp | port |
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
+----+---------------------+------+
1 row in set (0.0010 sec)
Copyright @ 2022 Oracle and/or its affiliates.
23

26. LAB 1: inserting data
Copyright @ 2022 Oracle and/or its affiliates.
24

27. MySQL InnoDB ReplicaSet
Easy Setup and Manual Failover
Copyright @ 2022 Oracle and/or its affiliates.
25

28. MySQL InnoDB ReplicaSet - our needs
Now, we need to have a solution in case our MySQL instance crashes and cannot be
restarted.
We also need, when possible, to o load some read queries to another instance.
Our RPO can be greater than 0.
Our RTO can be de ned in several minutes.
Copyright @ 2022 Oracle and/or its affiliates.
26

29. MySQL InnoDB ReplicaSet - our needs
Now, we need to have a solution in case our MySQL instance crashes and cannot be
restarted.
We also need, when possible, to o load some read queries to another instance.
Our RPO can be greater than 0.
Our RTO can be de ned in several minutes.
RPO: Recovery Point Objective (how much data can be lost)
RTO: Recovery Time Objective (how long to recover)
Copyright @ 2022 Oracle and/or its affiliates.
26

30. Based on the popular MySQL
Asynchronous Replication
Failover is Manual
Fully integrated with MySQL Shell and
MySQL Router
Data provisioning included (CLONE)
Recommended for unstable networks
RPO != 0 & RTO = minutes
MySQL InnoDB ReplicaSet
Copyright @ 2022 Oracle and/or its affiliates.
27

31. LAB 2
Copyright @ 2022 Oracle and/or its affiliates.
28

32. We use again MySQL Shell to deploy
another instance:
JS> dba.deploySandboxInstance(3320,
{password: 'MySQL123'})
LAB 2: deployment of a second MySQL sandbox
Copyright @ 2022 Oracle and/or its affiliates.
29

33. LAB 2: MySQL instances con guration
We need to con gure the instances so that they are ready to be part of a MySQL InnoDB
ReplicaSet:
JS> dba.configureReplicaSetInstance("root@localhost:3310")
JS> dba.configureReplicaSetInstance("root@localhost:3320")
Copyright @ 2022 Oracle and/or its affiliates.
30

34. LAB 2: MySQL instances con guration
We need to con gure the instances so that they are ready to be part of a MySQL InnoDB
ReplicaSet:
JS> dba.configureReplicaSetInstance("root@localhost:3310")
JS> dba.configureReplicaSetInstance("root@localhost:3320")
Copyright @ 2022 Oracle and/or its affiliates.
sandboxes are already con gured
30

35. LAB 2: MySQL instances con guration
< >
Copyright @ 2022 Oracle and/or its affiliates.
When I am not using a sandbox instance, MySQL Shell warns me about the root
user having access only from localhost.
It proposes 4 choices, what should I do?
31

36. LAB 2: MySQL instances con guration
< >
Copyright @ 2022 Oracle and/or its affiliates.
When I am not using a sandbox instance, MySQL Shell warns me about the root
user having access only from localhost.
It proposes 4 choices, what should I do?
The recommendation is to create a dedicated user to manage the solution on all
instances with the same credentials (option 2).
Check the example on the next slide !
31

37. LAB 2: MySQL instances con guration - example
Copyright @ 2022 Oracle and/or its affiliates.
32

38. We now create the MySQL InnoDB
ReplicaSet when connected to our rst
instance:
JS> rs=dba.createReplicaSet(
'myreplicaset')
LAB 2: MySQL InnoDB ReplicaSet creation
Copyright @ 2022 Oracle and/or its affiliates.
33

39. LAB 2: MySQL InnoDB ReplicaSet creation
Copyright @ 2022 Oracle and/or its affiliates.
34

40. LAB 2: MySQL InnoDB ReplicaSet creation
Explore the rs object created and get its status:
Copyright @ 2022 Oracle and/or its affiliates.
35

41. LAB 2: MySQL InnoDB ReplicaSet creation
Explore the rs object created and get its status:
JS> rs.status()
Copyright @ 2022 Oracle and/or its affiliates.
35

42. LAB 2: MySQL InnoDB ReplicaSet status
Copyright @ 2022 Oracle and/or its affiliates.
36

43. LAB 2: MySQL InnoDB ReplicaSet status
< >
Copyright @ 2022 Oracle and/or its affiliates.
When I created my ReplicaSet, I forgot to assign it to a variable...
What can I do ?
37

44. LAB 2: MySQL InnoDB ReplicaSet status
< >
Copyright @ 2022 Oracle and/or its affiliates.
When I created my ReplicaSet, I forgot to assign it to a variable...
What can I do ?
Just assing it again using the dba.ReplicaSet() method:
rs=dba.getReplicaSet()
37

45. It's time to add our second MySQL instance
to our MySQL InnoDB ReplicaSet:
JS> rs.addInstance('localhost:3320')
LAB 2: MySQL InnoDB ReplicaSet adding a member
Copyright @ 2022 Oracle and/or its affiliates.
38

46. LAB 2: MySQL InnoDB ReplicaSet adding a member
Copyright @ 2022 Oracle and/or its affiliates.
39

47. LAB 2: MySQL InnoDB ReplicaSet adding a member
Copyright @ 2022 Oracle and/or its affiliates.
40

48. Check again the status of the
MySQL InnoDB ReplicaSet
LAB 2: MySQL InnoDB ReplicaSet status
Copyright @ 2022 Oracle and/or its affiliates.
41

49. LAB 3
Copyright @ 2022 Oracle and/or its affiliates.
42

50. LAB 3: MySQL InnoDB ReplicaSet - test
In this lab, we will try to read and write data on both MySQL instances. Then we will
bootstrap MySQL Router and test it.
Copyright @ 2022 Oracle and/or its affiliates.
43

51. LAB 3: MySQL InnoDB ReplicaSet - test
In this lab, we will try to read and write data on both MySQL instances. Then we will
bootstrap MySQL Router and test it.
Connect to both instances on two di erent terminals (or tabs if you are using VS Code) and
list the records in the table perconalive.t1:
Copyright @ 2022 Oracle and/or its affiliates.
43

52. LAB 3: MySQL InnoDB ReplicaSet - test
In this lab, we will try to read and write data on both MySQL instances. Then we will
bootstrap MySQL Router and test it.
Connect to both instances on two di erent terminals (or tabs if you are using VS Code) and
list the records in the table perconalive.t1:
Copyright @ 2022 Oracle and/or its affiliates.
43

53. LAB 3: MySQL InnoDB ReplicaSet - test write
Now let's try to write on both instances:
SQL> insert into perconalive.t1 (port) values (@@port);
Copyright @ 2022 Oracle and/or its affiliates.
44

54. Primary Secondary
LAB 3: MySQL InnoDB ReplicaSet - test write
Now let's try to write on both instances:
SQL> insert into perconalive.t1 (port) values (@@port);
Copyright @ 2022 Oracle and/or its affiliates.
44

55. MySQL Router is very easy to con gure, you
only need to use the bootstrap
command:
$ sudo mysqlrouter --bootstrap
root@localhost:3310 --user mysqlrouter
$ sudo systemctl start mysqlrouter
It's also possible to create a MySQL user
account for Router (optional):
JS> rs.setupRouterAccount("router")
LAB 3: MySQL Router
Copyright @ 2022 Oracle and/or its affiliates.
45

56. MySQL Router is very easy to con gure, you
only need to use the bootstrap
command:
$ sudo mysqlrouter --bootstrap
root@localhost:3310 --user mysqlrouter
$ sudo systemctl start mysqlrouter
It's also possible to create a MySQL user
account for Router (optional):
JS> rs.setupRouterAccount("router")
LAB 3: MySQL Router
Copyright @ 2022 Oracle and/or its affiliates.
Windows users, info coming
45

57. LAB 3: MySQL Router
Copyright @ 2022 Oracle and/or its affiliates.
46

58. LAB 3: MySQL Router - Windows
Open a command terminal and bootstrap MySQL Router:
C:Usersfred>"C:Program FilesMySQLMySQL Router 8.0binmysqlrouter.exe"
--bootstrap root@localhost:3310 --directory=./router
Copyright @ 2022 Oracle and/or its affiliates.
47

59. And in the new terminal we run:
C:WINDOWSsystem32>"C:Program FilesMySQLMySQL Router 8.0bin
mysqlrouter.exe" --install-service-manual
-c "C:Usersfredroutermysqlrouter.conf"
LAB 3: MySQL Router - Windows
We need to install the Windows Service to start/stop MySQL Router.
We need to open a new command terminal but as an administrator:
Copyright @ 2022 Oracle and/or its affiliates.
48

60. And in the new terminal we run:
C:WINDOWSsystem32>"C:Program FilesMySQLMySQL Router 8.0bin
mysqlrouter.exe" --install-service-manual
-c "C:Usersfredroutermysqlrouter.conf"
LAB 3: MySQL Router - Windows
We need to install the Windows Service to start/stop MySQL Router.
We need to open a new command terminal but as an administrator:
Copyright @ 2022 Oracle and/or its affiliates.
one single line command !
48

61. LAB 3: MySQL Router - Windows
And you can now start the MySQL Router service manually:
Copyright @ 2022 Oracle and/or its affiliates.
49

62. LAB 3: MySQL Router
We have the possibility to list all MySQL Router registered with our ReplicaSet:
Copyright @ 2022 Oracle and/or its affiliates.
50

63. LAB 3: MySQL Router
We will now connect MySQL Shell via MySQL Router.
We use the following ports:
Read/Write: 6446
Read/Only: 6447
We will now use 3 terminals, all with MySQL Shell.
Copyright @ 2022 Oracle and/or its affiliates.
51

64. LAB 3: MySQL Router
JS> c root@localhost:3310
[3310] JS> rs=dba.getReplicaSet()
SQL> c root@localhost:6446
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
SQL> c root@localhost:6447
[6447] SQL> select * from perconalive.t1;
+----+---------------------+------+
| id | timestamp | port |
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
| 2 | 2022-05-04 20:41:15 | 3310 |
| 3 | 2022-05-04 21:27:45 | 3310 |
+----+---------------------+------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
52

65. LAB 3: MySQL Router - Change Primary (planned)
[3310] JS> rs.setPrimaryInstance('localhost:3320')
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
--> we need to reconnect
[6447] SQL> select * from perconalive.t1;
+----+---------------------+------+
| id | timestamp | port |
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
| 2 | 2022-05-04 20:41:15 | 3310 |
| 3 | 2022-05-04 21:27:45 | 3310 |
| 4 | 2022-05-04 21:54:18 | 3320 |
+----+---------------------+------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
53

66. LAB 3: MySQL Router - Change Primary (failure)
JS> dba.killSandboxInstance(3320)
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
ERROR: 2013 (HY000): Lost connection to MySQL server during query
The global session got disconnected..
Attempting to reconnect to 'mysql://root@localhost:6446'..............
The global session could not be reconnected automatically.
Please use 'reconnect' instead to manually reconnect.
[6447] SQL> select * from perconalive.t1;
ERROR: 2013 (HY000): Lost connection to MySQL server during query
The global session got disconnected..
Attempting to reconnect to 'mysql://root@localhost:6447'..
The global session was successfully reconnected.
+----+---------------------+------+
| id | timestamp | port |
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
...
| 4 | 2022-05-04 21:54:18 | 3320 |
+----+---------------------+------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
54

67. LAB 3: MySQL Router - Change Primary (failure)
JS> rs=dba.getReplicaSet()
JS> rs.status()
JS> rs.forcePrimaryInstance('localhost:3310')
[6446] SQL> reconnect
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
[6447] SQL> select * from perconalive.t1;
+----+---------------------+------+
| id | timestamp | port |
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
| 2 | 2022-05-04 20:41:15 | 3310 |
| 3 | 2022-05-04 21:27:45 | 3310 |
| 4 | 2022-05-04 21:54:18 | 3320 |
| 5 | 2022-05-04 22:05:35 | 3310 |
+----+---------------------+------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
55

68. MySQL InnoDB Cluster
High Availability and 0 data loss
Copyright @ 2022 Oracle and/or its affiliates.
56

69. MySQL InnoDB Cluster - our needs
Our business requires to have RPO=0 and to have automatic failover in case of problem.
We still need, when possible, to o load some read queries to another instance and
eventually write on multiple MySQL instances simultaneously.
Of course, our network is reliable and the latency is small.
Copyright @ 2022 Oracle and/or its affiliates.
57

70. Based on Group Replication
Failover is Automatic
Fully integrated with MySQL Shell and
MySQL Router
Data provisioning included (CLONE)
Writing to multiple nodes is possible (not
the default)
RPO = 0 & RTO = seconds
MySQL InnoDB Cluster
Copyright @ 2022 Oracle and/or its affiliates.
58

71. MySQL Group Replication
GR is a plugin for MySQL, made by MySQL and packaged with MySQL
GR is an implementation of the Replicated Database State Machine theory
GR's protocol is based on Paxos
GR allows to write on all Group Members (cluster nodes) simultaneously while retaining
consistency
GR implements con ict detection and resolution
GR allows automatic distributed recovery
Supported on all MySQL platforms !!
Linux, Windows, Solaris, OSX, FreeBSD
Copyright @ 2022 Oracle and/or its affiliates.
59

72. MySQL Group Replication
This means that with Group Replication and MySQL InnoDB Cluster:
it's not longer necessary to handle server fail-over manually
GR provides fault tolerance
GR enables update-everywhere setups
GR handles crashes, failures, re-connects automatically
allows an easy setup of a highly available MySQL service
Copyright @ 2022 Oracle and/or its affiliates.
60

73. MySQL Group Replication
This means that with Group Replication and MySQL InnoDB Cluster:
it's not longer necessary to handle server fail-over manually
GR provides fault tolerance
GR enables update-everywhere setups
GR handles crashes, failures, re-connects automatically
allows an easy setup of a highly available MySQL service
This is a solution for High Availability !
Copyright @ 2022 Oracle and/or its affiliates.
60

74. LAB 4
Copyright @ 2022 Oracle and/or its affiliates.
61

75. LAB 4: MySQL InnoDB Cluster
In lab4, we will rst deploy a new MySQL instance (sandbox).
Then we will "upgrade" (replace) our MySQL InnoDB ReplicaSet to InnoDB Cluster.
After, we will join the new instance.
Finally, we will recon gure MySQL Router for the cluster.
Copyright @ 2022 Oracle and/or its affiliates.
62

76. LAB 4: MySQL InnoDB Cluster
In lab4, we will rst deploy a new MySQL instance (sandbox).
Then we will "upgrade" (replace) our MySQL InnoDB ReplicaSet to InnoDB Cluster.
After, we will join the new instance.
Finally, we will recon gure MySQL Router for the cluster.
Let's restart the sandbox (3320) we killed at the end of lab 3:
JS> dba.startSandboxInstance(3320)
Copyright @ 2022 Oracle and/or its affiliates.
62

77. LAB 4: MySQL InnoDB Cluster
< >
Copyright @ 2022 Oracle and/or its affiliates.
If there is an error, where can I find more info ?
63

78. LAB 4: MySQL InnoDB Cluster
< >
Copyright @ 2022 Oracle and/or its affiliates.
If there is an error, where can I find more info ?
With MySQL 8.0, you can parse the error log directly from SQL. Try this:
select * from performance_schema.error_log order by logged desc limit 10;
63

79. Deploy a new MySQL instance next to our
current MySQL InnoDB ReplicaSet
JS> dba.deploySandboxInstance(3330,
{password: 'MySQL123'})
LAB 4: MySQL InnoDB Cluster
Copyright @ 2022 Oracle and/or its affiliates.
64

80. We dissolve the MySQL InnoDB ReplicaSet:
On the Primary:
[3310] JS> dba.dropMetadataSchema()
On the Secondary:
[3320] SQL> stop replica;
[3320] SQL> reset replica all;
LAB 4: MySQL InnoDB Cluster - dissolve
Copyright @ 2022 Oracle and/or its affiliates.
65

81. We now create the new
MySQL InnoDB Cluster:
On the Primary:
[3310] JS> cluster=dba.createCluster(
'mycluster')
[3310] JS> cluster.addInstance(
'localhost:3320')
[3310] JS> cluster.status()
LAB 4: MySQL InnoDB Cluster - creation
Copyright @ 2022 Oracle and/or its affiliates.
66

82. We add the third instance to our new
MySQL InnoDB Cluster.
For automatic HA, we need to have at least 3 nodes and an odd
amount of nodes is recommended.
On the new instance
JS> c root@localhost:3330
[3330] JS> dba.configureInstance()
[3330] JS> c root@localhost:3310
[3310] JS> cluster=dba.getCluster()
[3310] JS> cluster.addInstance(
'localhost:3330')
[3310] JS> cluster.status()
LAB 4: MySQL InnoDB Cluster - creation
Copyright @ 2022 Oracle and/or its affiliates.
67

83. LAB 4: MySQL InnoDB Cluster - status
Copyright @ 2022 Oracle and/or its affiliates.
68

84. It's time to recon gure and restart MySQL
Router
$ sudo mysqlrouter --bootstrap
root@localhost:3310
--user mysqlrouter
--conf-use-gr-notifications
--force
$ sudo systemctl restart mysqlrouter
LAB 4: MySQL InnoDB Cluster - Router
Copyright @ 2022 Oracle and/or its affiliates.
69

85. LAB 5
Copyright @ 2022 Oracle and/or its affiliates.
70

86. LAB 5: MySQL InnoDB Cluster
We will now connect again MySQL Shell via MySQL Router.
We use the following ports (same as for ClusterSet):
Read/Write: 6446
Read/Only: 6447
And we will still use 3 terminals with MySQL Shell.
Copyright @ 2022 Oracle and/or its affiliates.
71

87. LAB 5: MySQL InnoDB Cluster
JS> c root@localhost:3310
[3310] JS> cluster=dba.getCluster()
SQL > c root@localhost:6446
[6446] SQL > insert into perconalive.t1 (port) values (@@port);
SQL > c root@localhost:6447
[6447] SQL> select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 7 | 2022-05-05 14:24:54 | 3310 | 3330 |
+----+---------------------+------+-----------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
72

88. LAB 5: MySQL InnoDB Cluster - change Primary
[3310] JS> cluster.setPrimaryInstance('localhost:3320')
--> reconnect
[6446] SQL > insert into perconalive.t1 (port) values (@@port);
[6447] SQL > select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 8 | 2022-05-05 14:35:03 | 3320 | 3330 |
+----+---------------------+------+-----------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
73

89. LAB 5: MySQL InnoDB Cluster - failure
[3310] JS> dba.killSandboxInstance(3320)
--> reconnect
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
[6447] SQL> select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 9 | 2022-05-05 14:38:16 | 3310 | 3330 |
+----+---------------------+------+-----------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
74

90. LAB 5: MySQL InnoDB Cluster - failure
[3310] JS> dba.killSandboxInstance(3320)
--> reconnect
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
[6447] SQL> select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 9 | 2022-05-05 14:38:16 | 3310 | 3330 |
+----+---------------------+------+-----------+
Don't forget to check the output of cluster.status() !
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
74

91. LAB 5: MySQL InnoDB Cluster - mode
[3310] JS> dba.startSandboxInstance(3320)
[3310] JS> cluster.switchToMultiPrimaryMode()
--> reconnect
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
[6447] SQL> select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 10 | 2022-05-05 14:44:04 | 3310 | 3330 |
+----+---------------------+------+-----------+
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
75

92. LAB 5: MySQL InnoDB Cluster - mode
[3310] JS> dba.startSandboxInstance(3320)
[3310] JS> cluster.switchToMultiPrimaryMode()
--> reconnect
[6446] SQL> insert into perconalive.t1 (port) values (@@port);
[6447] SQL> select *, @@port `read_from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read_from |
+----+---------------------+------+-----------+
| 10 | 2022-05-05 14:44:04 | 3310 | 3330 |
+----+---------------------+------+-----------+
Don't forget to check the output of cluster.status() !
Copyright @ 2022 Oracle and/or its affiliates.
RW: 6446
RO: 6447
75

93. LAB 5: MySQL InnoDB Cluster - mode
< >
Copyright @ 2022 Oracle and/or its affiliates.
I'm trying to write multiple times... even making new connections but it seems
all writes are made on same instance, I expected to write on all nodes !
76

94. LAB 5: MySQL InnoDB Cluster - mode
< >
Copyright @ 2022 Oracle and/or its affiliates.
I'm trying to write multiple times... even making new connections but it seems
all writes are made on same instance, I expected to write on all nodes !
All nodes have the possibility to receive writes, the default policy it to always
use the first one. Try to change the strategy for [routing:bootstrap_rw] to
routing_strategy=round-robin in router's config file and restart it.
76

95. MySQL InnoDB ClusterSet
High Availability and Disaster Recovery
Copyright @ 2022 Oracle and/or its affiliates.
77

96. MySQL InnoDB ClusterSet
High Availability is perfect ! But this is within a region... what can we do in case of
datacenter issue ?
And how do we deal with all the topoly changes ?
And data provisioning ?
Copyright @ 2022 Oracle and/or its affiliates.
78

97. MySQL InnoDB ClusterSet
Copyright @ 2022 Oracle and/or its affiliates.
79

98. High Availability
(failure within a region)
RPO = 0
RTO = seconds (automatic failover)
Disaster Recovery (region failure)
RPO != 0
RTO = minutes or more (manual failover)
No write performance impact
MySQL InnoDB ClusterSet
Copyright @ 2022 Oracle and/or its affiliates.
80

99. LAB 6
Copyright @ 2022 Oracle and/or its affiliates.
81

100. We need to deploy 3 new
instances (secondary region).
JS> dba.deploySandboxInstance(4410,
{password: 'MySQL123'})
JS> dba.deploySandboxInstance(4420,
{password: 'MySQL123'})
JS> dba.deploySandboxInstance(4430,
{password: 'MySQL123'})
LAB6: MySQL InnoDB ClusterSet - deploy
Copyright @ 2022 Oracle and/or its affiliates.
82

101. LAB6: MySQL InnoDB ClusterSet - creation
Before the creation of the MySQL InnoDB ClusterSet we need to switch back our Cluster to
Single-Primary mode:
JS> c root@localhost:3301
[3310] JS> cluster.getCluster()
[3310] JS> cluster.switchToSinglePrimaryMode()
Now we can create our new ClusterSet. This is a method of a cluster object:
[3310] JS> cs=cluster.createClusterSet('mydomain')
Copyright @ 2022 Oracle and/or its affiliates.
83

102. This illustrates what we just
created.
Let's have a look at the status
of our new ClusterSet:
LAB6: MySQL InnoDB ClusterSet - creation
Copyright @ 2022 Oracle and/or its affiliates.
84

103. LAB6: MySQL InnoDB ClusterSet
Like for the other status() methods, ClusterSet supports the extended option.
Please try the following commands:
[3310] JS> cs.status{extended: 1})
[3310] JS> cs.status{extended: 2})
[3310] JS> cs.status{extended: 3})
Copyright @ 2022 Oracle and/or its affiliates.
85

104. LAB6: MySQL InnoDB ClusterSet
Like for the other status() methods, ClusterSet supports the extended option.
Please try the following commands:
[3310] JS> cs.status{extended: 1})
[3310] JS> cs.status{extended: 2})
[3310] JS> cs.status{extended: 3})
Get more info with cs.help('status')
or ? clusterset.status
Copyright @ 2022 Oracle and/or its affiliates.
85

105. It's time to create the Replica
Cluster. We start by adding one
instance from the other region:
JS> cluster2=
cs.createReplicaCluster(
'localhost:4420',
'mycluster2')
LAB6: MySQL InnoDB ClusterSet - Replica Cluster
Copyright @ 2022 Oracle and/or its affiliates.
86

106. LAB6: MySQL InnoDB ClusterSet - Replica Cluster
Copyright @ 2022 Oracle and/or its affiliates.
87

107. We need to add the other 2
instances to our Secondary
Cluster:
JS> cluster2.addInstance(
'localhost:4410')
JS> cluster2.addInstance(
'localhost:4430')
LAB6: MySQL InnoDB ClusterSet - Replica Cluster
Copyright @ 2022 Oracle and/or its affiliates.
88

108. LAB 7
Copyright @ 2022 Oracle and/or its affiliates.
89

109. LAB7: MySQL InnoDB ClusterSet - Router
What about the MySQL Router ? We already have one bootstrapped and running ?
Copyright @ 2022 Oracle and/or its affiliates.
90

110. LAB7: MySQL InnoDB ClusterSet - Router
Let's replace the con guration again:
$ sudo mysqlrouter --bootstrap root@localhost:3310
--user mysqlrouter --conf-use-gr-notifications --force
And restart MySQL Router:
$ sudo systemctl restart mysqlrouter
Copyright @ 2022 Oracle and/or its affiliates.
91

111. LAB7: MySQL InnoDB ClusterSet - Routing
MySQL InnoDB ClusterSet provides the possibility to de ne routing policies per Router
being registered in the ClusterSet.
Those Routing Policies can be changed ONLINE within MySQL Shell.
In a ClusterSet you can deploy 2 types of Routers:
targeting the PRIMARY to send writes to the PRIMARY cluster (and the PRIMARY node in
it)
targeting a speci c cluster to keep tra c local for example (writes not allowed)
It's also possible to de ne a policiy for INVALIDATED clusters.
Copyright @ 2022 Oracle and/or its affiliates.
92

112. LAB7: MySQL InnoDB ClusterSet - Routing Options
We can use the routingOptions() method of the ClusterSet object to list the current
routing policies:
Copyright @ 2022 Oracle and/or its affiliates.
93

113. LAB7: MySQL InnoDB ClusterSet - Routing Options
We can use the routingOptions() method of the ClusterSet object to list the current
routing policies:
Let's change the Policy of our MySQL Router to only send tra c to our local datacenter in
region 2:
JS> cs.setRoutingOption('imac::system', 'target_cluster', 'mycluster2')
Routing option 'target_cluster' successfully updated in router 'imac::system'.
Copyright @ 2022 Oracle and/or its affiliates.
Region 1
3310, 3320, 3330
Region 2
4410, 4420, 4430
93

114. SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4410 |
+----+---------------------+------+-----------+
1 row in set (0.0006 sec)
SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4420 |
+----+---------------------+------+-----------+
1 row in set (0.0006 sec)
LAB7: MySQL InnoDB ClusterSet - Routing Options
Now try to connect with MySQL Shell on port 6446 and 6447:
SQL> c root@localhost:6446
As the routing target is not PRIMARY (or not the Primary cluster) writes
are not allowed !
Copyright @ 2022 Oracle and/or its affiliates.
cs.setRoutingOption('imac::system',
'target_cluster', 'mycluster2')
94

115. SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4410 |
+----+---------------------+------+-----------+
1 row in set (0.0006 sec)
SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4420 |
+----+---------------------+------+-----------+
1 row in set (0.0006 sec)
LAB7: MySQL InnoDB ClusterSet - Routing Options
Now try to connect with MySQL Shell on port 6446 and 6447:
SQL> c root@localhost:6446
As the routing target is not PRIMARY (or not the Primary cluster) writes
are not allowed !
Copyright @ 2022 Oracle and/or its affiliates.
cs.setRoutingOption('imac::system',
'target_cluster', 'mycluster2')
Don´t forget to set back the Routing Policy to PRIMARY:
JS> cs.setRoutingOption('imac::system', 'target_cluster', 'primary')
Routing option 'target_cluster' successfully updated in router 'imac::system'.
94

116. LAB 8
Copyright @ 2022 Oracle and/or its affiliates.
95

117. SQL> c root@localhost:6446
SQL> insert into perconalive.t1 (port)
values (@@port);
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 52 | 2022-05-06 09:50:36 | 4410 | 4410 |
+----+---------------------+------+-----------+
SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 52 | 2022-05-06 09:50:36 | 4410 | 4430 |
+----+---------------------+------+-----------+
LAB8: MySQL InnoDB ClusterSet - Region Switch
Now we will see how we can switch the PRIMARY role to another region. First as a planned
operation and then after a huge failure.
Planned Region Switch
JS> cs.setPrimaryCluster('mycluster2')
Copyright @ 2022 Oracle and/or its affiliates.
96

118. LAB8: MySQL InnoDB ClusterSet - Region Switch
Output Example
Copyright @ 2022 Oracle and/or its affiliates.
97

119. Now we can check the status:
LAB8: MySQL InnoDB ClusterSet - Region Switch
Unplanned Region Switch
Simulate the issue:
JS> dba.killSandboxInstance(4410);dba.killSandboxInstance(4420);dba.killSandboxInstance(4430)
Copyright @ 2022 Oracle and/or its affiliates.
98

120. LAB8: MySQL InnoDB ClusterSet - Region Switch
Unplanned Region Switch
We need to force the available secondary region to take over:
JS> cs.forcePrimaryCluster('mycluster')
Copyright @ 2022 Oracle and/or its affiliates.
99

121. SQL> c root@localhost:6446
SQL> insert into perconalive.t1 (port)
values (@@port);
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3310 |
+----+---------------------+------+-----------+
SQL> c root@localhost:6447
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3320 |
+----+---------------------+------+-----------+
SQL> reconnect
SQL> select *, @@port `read from`
from perconalive.t1 order by id desc limit 1;
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3330 |
+----+---------------------+------+-----------+
LAB8: MySQL InnoDB ClusterSet - Region Switch
We can perform again read and writes via MySQL Router:
Copyright @ 2022 Oracle and/or its affiliates.
100

122. Now we can check the status:
LAB8: MySQL InnoDB ClusterSet - Region Switch
Unplanned Region Switch
When the o ine region is back:
JS> dba.startSandboxInstance(4410);dba.startSandboxInstance(4420);dba.startSandboxInstance(4430)
Copyright @ 2022 Oracle and/or its affiliates.
101

123. JS> c root@localhost:4410
JS > mycluster2=dba.rebootClusterFromCompleteOutage()
The cluster will rejoin automatically the
ClusterSet.
JS> dba.getClusterSet().status()
LAB8: MySQL InnoDB ClusterSet - Region Switch
Unplanned Region Switch
Now we need to connect to one instance of the cluster that failed and restart the cluster:
Copyright @ 2022 Oracle and/or its affiliates.
102

124. LAB 9
Copyright @ 2022 Oracle and/or its affiliates.
103

125. LAB9: MySQL InnoDB ClusterSet - Complete Outage
If everything was abruptly stopped, how can we put back the system ?
Copyright @ 2022 Oracle and/or its affiliates.
104

126. LAB9: MySQL InnoDB ClusterSet - Complete Outage
Copyright @ 2022 Oracle and/or its affiliates.
105

127. LAB9: MySQL InnoDB ClusterSet - Complete Outage
Copyright @ 2022 Oracle and/or its affiliates.
106

128. LAB9: MySQL InnoDB ClusterSet - Complete Outage
Copyright @ 2022 Oracle and/or its affiliates.
107

129. LAB9: MySQL InnoDB ClusterSet - Complete Outage
Copyright @ 2022 Oracle and/or its affiliates.
108

130. Copyright @ 2022 Oracle and/or its affiliates.
109

131. Thank you !
Copyright @ 2022 Oracle and/or its affiliates.
110

133. Share your ❤to MySQL
#mysql
Join our slack channel!
bit.ly/mysql-slack
Copyright @ 2022 Oracle and/or its affiliates.
112