Hkosc group replication-lecture_lab07

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |
Creating MySQLGroup Replicaiton
with Router
Ivan Ma
馬楚成
2016-June
February Copyright 2015, Oracle

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
2

Our Goal
3
Experiencing
MySQL Group Replicaiton &
MySQL Router
Experiencing
MySQL Group Replicaiton &
MySQL Router

Program Agenda
4
What is Group Replication?
Group Replication Use Cases
Setting up Group Replication
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
5

MySQL
Replication
Group
Replication*
Shared Disk/
Virtualization Solutions
MySQL Cluster
MySQL High Availability Solutions
99 99 .. 99 99 99 %%
5
*In Labs*In Labs

Replication Concept
• Group Replication Strategy
• Synchronized Replication
• Topology of Group Replication
- Master-Master(s)

MySQL Group Replication (InnoDB Engine)
Group Replication
“Multi-master update anywhere replication plugin for MySQL with built-in
automaticconflict detection,distributedrecovery and group membership.”
7

Group MySQL Replication - Active/Active Update
Anywhere
8
M M M M M
Com. API
Replication
Plugin
API
MySQL
Server
Group Comm.
System (Corosync)
Group Communication
System
Clients
ReplicationGroup

Program Agenda
9
Setting up Group Replication
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
5

The good thing about MySQL Group Replication
Group Replication Plugin
–Auto- Switch over
–Providing highly available database services
–Flexibility – to add or remove MySQL Nodes
10

The good things about MySQL Group Replication
Group Replication Plugin
–Simple Installation
–HA: If there are many server nodes ins offline status, still working
–Group Replication – All nodes provides full set of data by Replication
11

Requirements (by Design)
• Only Support InnoDB engine
• Requires Primary Key(for rowid indentification)
• Global Transaction Identifiers (GTIDs)
• Optimistic execution: transactions may abort on COMMIT due to conflicts
with concurrent transactions on other members
12

Full GTID support!
• All group members share the same UUID, the group name.
13
M M M M M
INSERT y;
Will have GTID: group_name:2
INSERT x;

Full GTID support!
• Users can specify the identifier for the transaction.
14
M M M M M
INSERT y;
SET GTID_NEXT= “UUID:50”
INSERT x;

Full GTID support!
• You can even replicate from a outside server to a group, global identifiers
will be preserved.
15
M M M M M
Conflictswill be detected!

Auto-increment configuration/handling
• Group is configured not to generate the same auto-increment value on all
members.
16
M M M M M
INSERT y;
y: 4
INSERT z;
z: 11
INSERT x;
x: 1

[1]: http://mysqlhighavailability.com/mysql-group-replication-auto-increment-configuration-handling/
• By default, the offset is provided by server_id and increment is 7 [1].
17
M M M M M
INSERT y;
y: 4
INSERT z;
z: 11
INSERT x;
x: 1
server_id: 1
server_id: 4

• Users can change the increment size to their needs using
GROUP_REPLICATION_AUTO_INCREMENT_INCREMENT option.
18
M M M M M
INSERT y;
y: 4
INSERT z;
z: 11
INSERT x;
x: 1
server_id: 1
server_id: 4

Program Agenda
19
Setting Up Group Replication
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
5

Basics of Installing MySQL Group Replication for MySQL
• MySQL 5.7.10
• MySQL Group Replication Plugin – Lab 0.7
– MySQL Labs :: MySQL Group Replication for MySQL Server 5.7.10
– http://labs.mysql.com/
– group_replication.so / group_replication.dll
20

Set Most Group Replication Variables in my.cnf
or (Startup parameters)
• The local node address (host, channel)
– /etc/hosts [ 127.0.0.1 primary ]
– Instances: primary:3306, primary:3316
• The group nodes peer addresses (a group of host and channels)
– group_replication_peer_addresses=primary:4306,primary:4316
– group_replication_local_address=primary:4306(for 3306)
– group_replication_local_address=primary:4316(for 3316)
– group_replication_recovery_user=rpl_user
– group_replication_recovery_password=rpl_pass
• Plugin location and loading plugin
22

Sample : 3306
• [mysqld]
• datadir=/home/mysql/data
• basedir=/usr
• port=3306
• socket=/home/mysql/data/my.sock
• log-bin
• binlog-format=row
• binlog-checksum=NONE
• server-id=101
• gtid-mode=on
• enforce-gtid-consistency=true
• log-slave-updates=true
• master-info-repository=TABLE
• relay-log-info-repository=TABLE
23
• # Extraction Algorithm
• transaction-write-set-extraction=MURMUR32
• plugin-load=group_replication.so
• group_replication_group_name=8a94f357-aab4-11df-86ab-c80aa9429562
• group_replication_recovery_retry_count=2
• group_replication_recovery_reconnect_interval=120
• group_replication_local_address=primary:4306
• group_replication_peer_addresses=primary:4306,primary:4316
• group_replication_bootstrap_group=1
• group_replication_start_on_boot=0
• group_replication_recovery_user=rpl_user
• group_replication_recovery_password=rpl_pass

Set Up Group Replication
00-createdb.sh Create the 2 databases
01-startdb.sh StartUp 2 database instances (3306 and 3316) with
standard configuration (no plugin installed)
02-mysqlupgrade.sh Not Necessary!!!
JUST IN CASE, the database does not have the latest
version from the PLUGIN.
03-createRpl.sh Create replication user on the 2 database instances
e.g. rpl_user / rpl_pass
04-restart-with-gcs.sh Restartthe 2 database instances with GROUP
REPLICATION configuration
05-setgrp.sh Set up the GROUP REPLICATION for the 2 instances
and
START GROUP_REPLICATION;
xx-chkgcs.sh <port> Check the status of the GROUP REPLICATION
24

00-createdb.sh
• CreateDatabase using “mysqld --initializate”
– --initialize-insecure : To initialize the database with “root” and empty password
– Initialize 2 databases
• /home/mysql/data
• /home/mysql/data2
25
rm -rf /home/mysql/data
rm -rf /home/mysql/data2
mysqld --initialize-insecure --user=mysql --
explicit_defaults_for_timestamp --basedir=/usr/local/mysql --
datadir=/home/mysql/data
mysqld --initialize-insecure --user=mysql --
explicit_defaults_for_timestamp --basedir=/usr/local/mysql --
datadir=/home/mysql/data2

• [mysqld]
• datadir=/home/mysql/data
• basedir=/usr
• port=3306
• socket=/home/mysql/data/my.sock
• log-bin
• server-id=101
• gtid-mode=on
• [mysqld]
• datadir=/home/mysql/data2
• basedir=/usr
• port=3316
• socket=/home/mysql/data2/my.sock
• log-bin
• server-id=102
• gtid-mode=on
26
01-startdb.sh
mysqld --defaults-file=config/my.cnf >
/home/mysql/data/my.log 2>&1 &
mysqld --defaults-file=config/my2.cnf >
/home/mysql/data2/my.log 2>&1 &
my.cnf my.2cnf

03-createRpl.sh
• Creating the Replication Recovery User : rpl_user / rpl_pass
• Granting the “replication slave”
27
mysql -uroot -h127.0.0.1 -P3306 -e "grant replication slave on *.* to rpl_user@'%' identified by 'rpl_pass';“
mysql -uroot -h127.0.0.1 -P3316 -e "grant replication slave on *.* to rpl_user@'%' identified by 'rpl_pass';”

• Port = 3306
• grouop_replication_bootstrap_group=1
• Port = 3316
• grouop_replication_bootstrap_group=0
28
04-restart-with-gcs.sh
mysqladmin -uroot -h127.0.0.1 -P3306 shutdown
mysqladmin -uroot -h127.0.0.1 -P3316 shutdown
sleep 5
mysqld --defaults-file=config/myG1.cnf --plugin-load=group_replication.so --group_replication_bootstrap_group=1 --group-
replication_start_on_boot=0
> /home/mysql/data/my.log 2>&1 &
mysqld --defaults-file=config/myG2.cnf --plugin-load=group_replication.so --group_replication_bootstrap_group=0 --group-
replication_start_on_boot=0
> /home/mysql/data2/my.log 2>&1 &

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. | 29
MySQL Group Replication Settings
• #myG1.cnf (in addition to my.cnf) - 3306
• group_replication_group_name=8a94f357-aab4-11df-86ab-
c80aa9429562
• #myG2.cnf (In addition to my2.cnf) - 3316
• group_replication_group_name=8a94f357-aab4-11df-86ab-
c80aa9429562

05-setgrp.sh
Starting Up Group Replication (bootstrap)
• Setup the Recovery User for channel ‘group_replication_recovery’
• Start the bootstrap FIRST (3306) with setting group_replication_bootstrap_group=1
•
30
mysql -uroot -h127.0.0.1 -P3306 << EOL1
reset master;
reset slave;
SET GLOBAL group_replication_group_name= "8a94f357-aab4-11df-86ab-c80aa9429562";
SET GLOBAL group_replication_recovery_retry_count= 2;
SET GLOBAL group_replication_recovery_reconnect_interval=120;
SET GLOBAL group_replication_local_address="primary:4306";
SET GLOBAL group_replication_peer_addresses="primary:4306,primary:4316";
show warnings;
EOL1

05-setgrp.sh
Starting Up Group Replication (other than bootstrap)
• Setup the Recovery User for channel ‘group_replication_recovery’
• Start other instances with setting group_replication_bootstrap_group=0
•
31
mysql -uroot -h127.0.0.1 -P3316 << EOL2
reset master;
reset slave;
SET GLOBAL group_replication_group_name= "8a94f357-aab4-11df-86ab-c80aa9429562";
SET GLOBAL group_replication_recovery_retry_count= 2;
SET GLOBAL group_replication_recovery_reconnect_interval=120;
SET GLOBAL group_replication_local_address="primary:4316";
SET GLOBAL group_replication_peer_addresses="primary:4306,primary:4316";
show warnings;
EOL2

xx-chkgcs.sh <port>
32
mysql -uroot -h127.0.0.1 -P$1 << EOL2
SELECT * FROM performance_schema.replication_connection_statusG
SELECT * FROM performance_schema.replication_group_members;
SELECT * FROM performance_schema.replication_group_member_statsG
EOL2
*************************** 1. row ***************************
CHANNEL_NAME: group_replication_applier
GROUP_NAME: 8a94f357-aab4-11df-86ab-c80aa9429562
…
SERVICE_STATE: ON
…
RECEIVED_TRANSACTION_SET: 8a94f357-aab4-11df-86ab-c80aa9429562:1-8
…
*************************** 2. row ***************************
CHANNEL_NAME: group_replication_recovery
GROUP_NAME:
…
SERVICE_STATE: OFF
…
CHANNEL_NAME MEMBER_ID MEMBER_HOST MEMBER_PORT MEMBER_STATE
group_replication_applier 1ada3020-1d99-11e6-b299-080027558cda virtual-102.localhost 3306 ONLINE
group_replication_applier 1de2e5fb-1d99-11e6-b51a-080027558cda virtual-102.localhost 3316 ONLINE
*************************** 1. row ***************************
VIEW_ID: 14639729171658053:8
MEMBER_ID: 1ada3020-1d99-11e6-b299-
080027558cda
COUNT_TRANSACTIONS_IN_QUEUE: 0
COUNT_TRANSACTIONS_CHECKED: 0
COUNT_CONFLICTS_DETECTED: 0
COUNT_TRANSACTIONS_VALIDATING: 0
TRANSACTIONS_COMMITTED_ALL_MEMBERS: 8a94f357-aab4-11df-86ab-
c80aa9429562:1-8
LAST_CONFLICT_FREE_TRANSACTION: 8a94f357-aab4-11df-86ab-
c80aa9429562:8

Limitations
• Concurrent DDL is unsupported
• CTAS (Create Table As SELECT) is unsupported
– GTID Consistency (Not because of the GROUP REPLICATION)
33

Program Agenda
34
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
5

Conflict Resolution
•There is global total order for transactions
•All servers apply the same set of changes in the same
order, therefore they remain consistent within the group
–First committer wins
35

Multi-Master: Update Anywhere
• Any two transactions on differentserverscan write to the same row
• Conflictswill automatically be detected and handled
36
M M M M M
BEGIN;
UPDATE t1 SET c1=2
WHERE C1 =0;
TRX2,node 4:
M M M M M
BEGIN;
UPDATE t1 SET c1=1
WHERE C1=0;
TRX1,node 1:

• TRX1commits
• TRX2rollbacks
37
M M M M M
COMMIT;
but Rollback
TRX2,node 4:
M M M M M
COMMIT;
TRX1,node 1:
OK

• TRX1commits
• TRX2rollbacks
38
M M M M M
BEGIN;
UPDATE t1 SET c1=2
WHERE C1 =0;
TRX2,node 4:
M M M M M
BEGIN;
UPDATE t1 SET c1=1
WHERE C1=0;
TRX1,node 1:
OK
M M M M M
Consistency!
SELECT * FROM T1;
c1 =1

Group Replication Agenda
39
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
5

Recovery in Group Replication
•Recovery is run when a new node is added
•Recovery is run when a node that had previously been
added but has been offline comes back online
40

Automatic Distributed Server Recovery
• Node that joins the group automatically synchronizes with other
nodes
41
M M M M M N
Setto join group

• Node that joins the group automatically synchronizes with other
nodes
42
M M M M M N
ONLINE
RECOVERING

• Node that joins the group automatically synchronized with other
nodes
43
M M M M M M
ONLINE

Group Replication Agenda
45
Installing 5.7 and Group Replication Plugin
Conflict Resolution
Recovery
DBA Tools
2
3
4
5
1
6

Check Settings of Group Replication
47
mysql SELECT * FROM performance_schema.replication_group_member_statsG
*************************** 1. row ***************************
1 row in set (0.00 sec)
mysql> SELECT * FROM performance_schema.replication_group_member_statsG
*************************** 1. row ***************************
VIEW_ID: 235307401:3
MEMBER_ID: a236a0ec-9e9b-11e5-8be3-8b41a7829667
COUNT_TRANSACTIONS_IN_QUEUE: 0
COUNT_TRANSACTIONS_CHECKED: 12
COUNT_CONFLICTS_DETECTED: 5
COUNT_TRANSACTIONS_VALIDATING: 6
TRANSACTIONS_COMMITTED_ALL_MEMBERS:
LAST_CONFLICT_FREE_TRANSACTION: 8a94f357-aab4-11df-86ab-c80aa9429562:3
1 row in set (0.00 sec)

Disaster Recovery
Backup and Restore
High Availability
MySQL Enterprise Edition – Business
Durability
48

And More
Security
Monitoring
Backup
24x7 Support
MySQL Enterprise
Engineering
49

Learn More
http://mysqlhighavailability.com/tag/mysql-group-replication/
• MySQL Group Replication Install Information
• News/Updates
• Blogs
http://labs.mysql.com
• Download and evaluate all MySQL Group Replication from
the labs
50

Hkosc group replication-lecture_lab07

Hkosc group replication-lecture_lab07

More Related Content

What's hot (20)

Similar to Hkosc group replication-lecture_lab07 (20)

More from Ivan Ma (16)

Recently uploaded (20)

Hkosc group replication-lecture_lab07