Percona Live 2022 - MySQL Architectures

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

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

Who am I ?
about.me/lefred
4

@lefred
MySQL Evangelist
using MySQL since version 3.20
devops believer
likes 🏀
living in
h ps://lefred.be
Frédéric Descamps
5

Housekeeping
some information
6

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, ...
7

MySQL Shell is now included in Visual Studio Code:
8

9

Windows Users - Installation
For Microsoft Windows users, please use MySQL Installer to install the required products:
10

MySQL Architectures
the Agenda in Pictures
11

We will start with the deployment of a
single instance of MySQL.
MySQL architectures: Agenda
12

We will create a second instance and setup
Asynchronous replication.
We will also deploy MySQL Router.
13

We will then upgrade to MySQL InnoDB
Cluster and add a third MySQL instance.
14

To nish with the ultimate High Availability and Disaster Recovery solution:
15

MySQL
Single Instance
16

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
17

LAB 1
18

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'})
19

20

Now we can connect to our sandbox MySQL instance:
JS> c root@localhost:3310
root / MySQL123
port: 3310
21

root / MySQL123
port: 3310
22

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);
23

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)
23

24

MySQL InnoDB ReplicaSet
Easy Setup and Manual Failover
25

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.
26

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)
26

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
27

LAB 2
28

We use again MySQL Shell to deploy
another instance:
JS> dba.deploySandboxInstance(3320,
{password: 'MySQL123'})
LAB 2: deployment of a second MySQL sandbox
29

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")
30

We need to con gure the instances so that they are ready to be part of a MySQL InnoDB
ReplicaSet:
sandboxes are already con gured
30

< >
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

< >
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

LAB 2: MySQL instances con guration - example
32

We now create the MySQL InnoDB
ReplicaSet when connected to our rst
instance:
JS> rs=dba.createReplicaSet(
'myreplicaset')
LAB 2: MySQL InnoDB ReplicaSet creation
33

34

Explore the rs object created and get its status:
35

Explore the rs object created and get its status:
JS> rs.status()
35

LAB 2: MySQL InnoDB ReplicaSet status
36

< >
When I created my ReplicaSet, I forgot to assign it to a variable...
What can I do ?
37

< >
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

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
38

39

40

Check again the status of the
41

LAB 3
42

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.
43

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:
43

LAB 3: MySQL InnoDB ReplicaSet - test write
Now let's try to write on both instances:
SQL> insert into perconalive.t1 (port) values (@@port);
44

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);
44

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
45

MySQL Router is very easy to con gure, you
only need to use the bootstrap
command:
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
Windows users, info coming
45

LAB 3: MySQL Router
46

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
47

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

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

And you can now start the MySQL Router service manually:
49

LAB 3: MySQL Router
We have the possibility to list all MySQL Router registered with our ReplicaSet:
50

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.
51

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

LAB 3: MySQL Router - Change Primary (planned)
[3310] JS> rs.setPrimaryInstance('localhost:3320')
--> we need to reconnect
+----+---------------------+------+
+----+---------------------+------+
| 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 |
+----+---------------------+------+
RW: 6446
RO: 6447
53

LAB 3: MySQL Router - Change Primary (failure)
JS> dba.killSandboxInstance(3320)
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.
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.
+----+---------------------+------+
+----+---------------------+------+
| 1 | 2022-05-04 16:30:06 | 3310 |
...
| 4 | 2022-05-04 21:54:18 | 3320 |
+----+---------------------+------+
RW: 6446
RO: 6447
54

LAB 3: MySQL Router - Change Primary (failure)
JS> rs=dba.getReplicaSet()
JS> rs.status()
JS> rs.forcePrimaryInstance('localhost:3310')
[6446] SQL> reconnect
+----+---------------------+------+
+----+---------------------+------+
| 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 |
+----+---------------------+------+
RW: 6446
RO: 6447
55

MySQL InnoDB Cluster
High Availability and 0 data loss
56

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.
57

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
58

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
59

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
60

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 !
60

LAB 4
61

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.
62

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)
62

< >
If there is an error, where can I find more info ?
63

< >
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

Deploy a new MySQL instance next to our
current MySQL InnoDB ReplicaSet
64

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
65

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
66

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
[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
67

LAB 4: MySQL InnoDB Cluster - status
68

It's time to recon gure and restart MySQL
Router
root@localhost:3310
--user mysqlrouter
--conf-use-gr-notifications
--force
$ sudo systemctl restart mysqlrouter
LAB 4: MySQL InnoDB Cluster - Router
69

LAB 5
70

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.
71

[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 |
+----+---------------------+------+-----------+
RW: 6446
RO: 6447
72

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`
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 8 | 2022-05-05 14:35:03 | 3320 | 3330 |
+----+---------------------+------+-----------+
RW: 6446
RO: 6447
73

LAB 5: MySQL InnoDB Cluster - failure
[3310] JS> dba.killSandboxInstance(3320)
--> reconnect
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 9 | 2022-05-05 14:38:16 | 3310 | 3330 |
+----+---------------------+------+-----------+
RW: 6446
RO: 6447
74

LAB 5: MySQL InnoDB Cluster - failure
[3310] JS> dba.killSandboxInstance(3320)
--> reconnect
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 9 | 2022-05-05 14:38:16 | 3310 | 3330 |
+----+---------------------+------+-----------+
Don't forget to check the output of cluster.status() !
RW: 6446
RO: 6447
74

LAB 5: MySQL InnoDB Cluster - mode
[3310] JS> dba.startSandboxInstance(3320)
[3310] JS> cluster.switchToMultiPrimaryMode()
--> reconnect
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 10 | 2022-05-05 14:44:04 | 3310 | 3330 |
+----+---------------------+------+-----------+
RW: 6446
RO: 6447
75

[3310] JS> dba.startSandboxInstance(3320)
[3310] JS> cluster.switchToMultiPrimaryMode()
--> reconnect
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 10 | 2022-05-05 14:44:04 | 3310 | 3330 |
+----+---------------------+------+-----------+
Don't forget to check the output of cluster.status() !
RW: 6446
RO: 6447
75

< >
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

< >
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

MySQL InnoDB ClusterSet
High Availability and Disaster Recovery
77

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 ?
78

79

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
80

LAB 6
81

We need to deploy 3 new
instances (secondary region).
LAB6: MySQL InnoDB ClusterSet - deploy
82

LAB6: MySQL InnoDB ClusterSet - creation
Before the creation of the MySQL InnoDB ClusterSet we need to switch back our Cluster to
Single-Primary mode:
[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')
83

This illustrates what we just
created.
Let's have a look at the status
of our new ClusterSet:
LAB6: MySQL InnoDB ClusterSet - creation
84

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})
85

LAB6: MySQL InnoDB ClusterSet
Like for the other status() methods, ClusterSet supports the extended option.
Please try the following commands:
Get more info with cs.help('status')
or ? clusterset.status
85

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
86

87

We need to add the other 2
instances to our Secondary
Cluster:
JS> cluster2.addInstance(
'localhost:4410')
JS> cluster2.addInstance(
'localhost:4430')
88

LAB 7
89

LAB7: MySQL InnoDB ClusterSet - Router
What about the MySQL Router ? We already have one bootstrapped and running ?
90

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
91

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.
92

LAB7: MySQL InnoDB ClusterSet - Routing Options
We can use the routingOptions() method of the ClusterSet object to list the current
routing policies:
93

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'.
Region 1
3310, 3320, 3330
Region 2
4410, 4420, 4430
93

SQL> select *, @@port `read from`
+----+---------------------+------+-----------+
| id | timestamp | port | read from |
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4410 |
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4420 |
+----+---------------------+------+-----------+
Now try to connect with MySQL Shell on port 6446 and 6447:
As the routing target is not PRIMARY (or not the Primary cluster) writes
are not allowed !
cs.setRoutingOption('imac::system',
'target_cluster', 'mycluster2')
94

+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4410 |
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 50 | 2022-05-05 14:46:52 | 3330 | 4420 |
+----+---------------------+------+-----------+
Now try to connect with MySQL Shell on port 6446 and 6447:
As the routing target is not PRIMARY (or not the Primary cluster) writes
are not allowed !
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

LAB 8
95

SQL> insert into perconalive.t1 (port)
values (@@port);
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 52 | 2022-05-06 09:50:36 | 4410 | 4410 |
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 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')
96

Output Example
97

Now we can check the status:
Unplanned Region Switch
Simulate the issue:
JS> dba.killSandboxInstance(4410);dba.killSandboxInstance(4420);dba.killSandboxInstance(4430)
98

We need to force the available secondary region to take over:
JS> cs.forcePrimaryCluster('mycluster')
99

SQL> insert into perconalive.t1 (port)
values (@@port);
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3310 |
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3320 |
+----+---------------------+------+-----------+
SQL> reconnect
+----+---------------------+------+-----------+
+----+---------------------+------+-----------+
| 53 | 2022-05-06 10:28:37 | 3310 | 3330 |
+----+---------------------+------+-----------+
We can perform again read and writes via MySQL Router:
100

Now we can check the status:
When the o ine region is back:
JS> dba.startSandboxInstance(4410);dba.startSandboxInstance(4420);dba.startSandboxInstance(4430)
101

JS > mycluster2=dba.rebootClusterFromCompleteOutage()
The cluster will rejoin automatically the
ClusterSet.
JS> dba.getClusterSet().status()
Now we need to connect to one instance of the cluster that failed and restart the cluster:
102

LAB 9
103

LAB9: MySQL InnoDB ClusterSet - Complete Outage
If everything was abruptly stopped, how can we put back the system ?
104

105

106

107

108

109

Thank you !
110

Share your ❤to MySQL
#mysql
Join our slack channel!
bit.ly/mysql-slack
112

Percona Live 2022 - MySQL Architectures

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Percona Live 2022 - MySQL Architectures

Similaire à Percona Live 2022 - MySQL Architectures (20)

Plus de Frederic Descamps

Plus de Frederic Descamps (12)

Dernier

Dernier (20)

Percona Live 2022 - MySQL Architectures