MySQL InnoDB Cluster and Group Replication

Madhusudhan G Joshi(madhusudhan.joshi@oracle.com)Software Development Manager

Sujatha Sivakumar(sujatha.sivakumar@oracle.com)Principal Member Technical Staf

Safe Harbour 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.

Program Agenda

Introduction to MySQL Innodb Cluster

How to get it working

Introduction to Group Replication

Look and Feel of GR!

Monitoring

Introduction to MySQL Innodb Cluster1

InnoDB ClusterIntegrated Solution● Group Replication for high availability.● Asynchronous Replication for Read Scale-out.● One-stop shell to deploy and manage the cluster.● Seamlessly and automatically route the workload to the proper database server in the cluster.● Hide failures from the application.

MySQL Connector

Application

MySQL Router

MySQL Connector

Application

MySQL Router

MQL Shell

S1 S2 S3 S4 S…

How to get it working2

MySQL InnoDB Cluster

• Start MySQL Shell• Deploy Instance (s)• dba.deploySandboxInstance(....)

• Start MySQL Shell• Deploy Instance (s)

• Initiate/Create ClusterInitiate/Create Cluster

shell.connect("root@localhost:1310");shell.connect("root@localhost:1310");

cluster = dba.createCluster('OSIcluster');cluster = dba.createCluster('OSIcluster');

few more moments ….

Is the Cluster on and available ?

• Start MySQL Shell• Deploy Instance (s)• Create Cluster

Add few more instancesAdd few more instances

myOSI.addInstance("root@localhost:XXXX");myOSI.addInstance("root@localhost:XXXX");

MySQL InnoDB ClusterHow is the InnoDB Cluster now ?

MySQL InnoDB Cluster• Start MySQL Shell• Deploy Instance (s)• Create Cluster• Add more instances

Setup and start RouterSetup and start Routerbin/mysqlrouter --bootstrap localhost:bin/mysqlrouter --bootstrap localhost:

1310 --name OSIRouter1310 --name OSIRouter

Notice the R/W, R ports for MySQL

InnoDB Cluster

MySQL Router( layered on top of the MySQL Instances )

‘R’ InstancePort :1311

‘R/W’ InstancePort :1310

Router is set and HA’d

MySQL InnoDB Cluster…on test

• Start MySQL Shell• Deploy Instance (s)• Create Cluster• Add more instances• Setup and Start Router

Client connects to R/W Instance Client connects to R/W Instance

and and

Kill R/W InstanceKill R/W Instance

Where do new client requests go to ???

MySQL InnoDB Cluster…on test

• Start MySQL Shell• Deploy Instance (s)• Create Cluster• Add more instances• Setup and Start Router• Client Connects to R/W Instance• Kill R/W Instance

Client Requests handled by new R/W InstanceClient Requests handled by new R/W Instance

How does the InnoDB Cluster look like ….now ???

MySQL Router( layered on top of the MySQL Instances )

‘R/W’ InstancePort :1311

Introduction to Group Replication3

MySQL Group ReplicationTraditional database● Many clients● One server

server

clients

MySQL Group Replication

serverA

serverB

serverC

clientsGroup Replication● Many clients● Many servers● Read scalability● Write everywhere*● Elastic,

Highly available● Agreement on:

● Members● Message delivery● State updates

serverA

serverB

serverC

R RR R RR

serverA

serverB

serverC

R W RW

clients

Group Replication● Many clients● Many servers● Read scalability● Write everywhere*● Elastic,

Limitations apply!https://dev.mysql.com/doc/refman/8.0/en/group-replication-limitations.html

serverA

serverB

serverC

R W RW

clients

serverD

serverA

serverB

serverC

WR R W RW

clients

serverD

serverE

serverA

serverB

serverC

R WR W RW

clients

serverD

serverE

serverA

serverB

serverC

R WR W RW

clients

serverD

serverE

serverA

serverB

serverC

R WR W RW

clients

serverE

serverA

serverB

serverC

R WR W RW

clients

serverE

serverA

serverB

serverC

R WR W RW

8.0 Operations: Set Next Primary

SET group_replication_member_weight = [0-100]

Dw=25 w=20

R RR R RR R RR

w=10w=35

Dw=10 w=25 w=20

R RR R RR R RR

Dw=10 w=25 w=20

W WW R RR R RR R RR

Dw=10 w=25 w=20

W WW R RR R RR R RR

25 is the biggest→ C is new primary

Dw=10 w=25 w=20

W WW R RR R RR R RR

8.0 Operations: No Writes After Leaving Group

Locally on A:

STOP GROUP REPLICATION

1. Disallow new writes2. Wait for ongoing writes3. Leave group

Locally on A:

STOP GROUP REPLICATION

Locally on A:STOP GROUP REPLICATION

serverA

serverB

serverC

R WR W RW

clients

We are 3:A, B, C!

serverA

serverB

serverC

R WR W RW

serverA

serverB

W RW R WR W RW

clients

You and me:A and B!

serverA

serverB

W RW R WR W RW

B B A A

All receive insame order

serverA

serverB

W RW R WR W RW

clients

Tablerow 1row 2row 3

insert row 4

Tablerow 1row 2

insert row 3insert row 4

serverA

serverB

W RW WR

clients

Group Replication● Non conflicting

transactions are

certified positive.● For Conflicting

transactions firstcommitter wins

UPDATE t1 SET a=3

WHERE a=1

UPDATE t1SET a=4

Where a=2

serverA

serverB

W RW WRclients

Group Replication● Non conflicting

transactions are

certified positive.● For Conflicting

transactions firstcommitter wins

UPDATE t1 SET a=3

WHERE a=1 UPDATE t1SET a=4

Where a=1OK

Look and Feel of GR!4

MySQL Group ReplicationGroup Replication● MySQL plugin● Uses InnoDB● Uses row format● Monitor using

performance schema● Full GTID support● Auto-increment

handling● Version access control

GR in 8 is gr8

MySQL Group ReplicationGroup Replication● MySQL plugin● Uses InnoDB● Monitor using

performance schema●

● Auto-increment

handling● Version access control

serverA

serverB

W RW WR

clients

INSERT x;Will have

GTID:UUID:1

INSERT y;Will have

GTID:UUID:2

Full GTID support

All group members share the same UUID, the group name.

performance schema● Full GTID support●

● Version access control

serverA

serverB

W RW WR

INSERT x;X:1

INSERT y;Y:2

INSERT z;Y:9

Auto-increment handling

●By default, the ofset is provided by server_id and increment is 7.●Users can change the increment size usinggroup_replication_auto_increment_increment

option.

handling

Version access control

5.7.13

5.7.14

5.7.15

R WR W RW

Member with different patch version is allowed to join the gorup.

5.7.16

handling

R WR W RW

Member with lower major version than the major version in the group is not allowed to join group.

5.7.16

handling

5.7.13

5.7.14

5.7.15

R WR W RW

Member with higher major version is allowed to join but is not allowed to do writes. (Read only)

MySQL Async Replication

Example: Async replication between geo-distributed groups

Replication Architecture: Applier Pipeline

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

8.0 Performance: Applier Pipeline Parallelize reads and writes to relay log

Performance for free

Replica

RelayLog

WorkerQueues

WorkerThreads

Coordinator Thread

ReceiverThread

network

Monitoring5

8.0 Monitoring: Group Members Who are in this group?

– server_uuid, host, port, MySQL version

Who is the primary? Online status of each node

mysql> SELECT … FROM performance_schema.replication_group_membersMEMBER_ID MEMBER_HOST MEMBER_PORT MEMBER_STATE MEMBER_ROLE MEMBER_VERSION<uuid-A> murkla 3306 ONLINE PRIMARY 5.7.20<uuid-B> kremla 3306 ONLINE SECONDARY 5.7.21<uuid-C> kantarell 3306 UNREACHABLE SECONDARY 8.0.3

New in 8.0

B5.7.21

A5.7.20

C8.0.3

8.0 Monitoring: Group Member Statistics Statistics used to diagnose group members

– Conflict ratio of the group– Conflict ratio of each member (multi-primary)– Is any member falling behind on certification or applying?

Table performance_schema.replication_group_member_stats:counts of transactions, by member:

– Positively/negatively certified transactions of any origin– Positively/negatively certified transactions from the node– Transactions waiting to be certified– Certified transactions waiting to be applied

“I can’t w8 to replic8 with version 8” Evalu8

http://www.mysql.com/downloads/

Educ8Innodb cluster:

https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-userguide.html

group replication:

http://dev.mysql.com/doc/refman/8.0/en/group-replication.html

Contempl8http://mysqlhighavailability.com

Cooper8https://bugs.mysql.com/

Thank You!& cu l8r, m8s

MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore

Transcript of MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore

MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore

Software

Transcript of MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore

MySQL Tech Tour 2015 - 5.7 InnoDB

What’s New in MariaDB Server 10 · Enhancements from MySQL InnoDB 5.7 Enable InnoDB NUMA interleave for InnoDB. LAYOUT Title Only ... Optimizer Enhancements ... PowerPoint Default

MySQL 和 InnoDB 性能

MySQL Group Replicatio in a nutshell - MySQL InnoDB Cluster

Dell Wyse Management Suite · Deploy high availability on MySQL InnoDB servers—see Deploy high availability on MySQL InnoDB. 4. Deploy high availability on MongoDB—see Deploy

MySQL Group Replication & MySQL InnoDB Cluster · MySQL Group Replication is a MySQL Server plugin that provides distributed state machine replication with strong coordination between

MySQL vs MariaDB - Amazon S3€¦ · InnoDB InnoDB MyISAM DDL Performance Smart Doublewrite Dynamic Buffer Pool More Transportable InnoDB as Default Spatial Indexes Improved Crash

MySQL Best Practices · MySQL InnoDB Cluster - MySQL Router - MySQL Shell 2018 MySQL 8.0 -Still GNU GPL v2-Data Dictionary - Roles-Unicode - CTEs - Window Functions - Security - Replication

InnoDB Scalability Limits€¦ · InnoDB Scalability Limits, MySQL Users Conference, Santa Clara,CA April 14-17 2008 What we'll talk about • MySQL's main transactional storage engine

3 / 147 · MySQL 8.0 InnoDB Cluster is a very easy High Availability solution for MySQL Frédéric Descamps - MySQL Community Manager - Oracle 4 / 147. ... Shared clusters Federated

MySQL Group Replication @osi days 2014

OSCON2004 MySQL Innodb Performance Optimization

MySQL InnoDB Storage Engine

MySQL 5.5 Guide to InnoDB Status

InnoDB Replacement with DeepDB for MySQL DrupalCon 2013

New InnoDB Features in MySQL 5

MySQL Storage Engines - which do you use? TokuDB? MyRocks? InnoDB?

Developing high-throughput services with no sql ap-is to innodb and mysql cluster

Innodb 1.1 for mysql 5.5 user's guide

MySQL 8 : The Best gets even better · 2018-07-27 · MySQL 5.7 MySQL InnoDB Cluster - MySQL Group Replication - MySQL Router - MySQL Shell MySQL 8.0 - NoSQL Document Store - JSON