Kenny Gryp, profile picture
Uploaded byKenny Gryp
3,259 views

MySQL Database Architectures - InnoDB ReplicaSet & Cluster

This document provides an overview and comparison of MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet. It discusses the components, goals, and features of each solution. MySQL InnoDB Cluster uses Group Replication to provide high availability, automatic failover, and data consistency. MySQL InnoDB ReplicaSet uses asynchronous replication and provides availability and read scaling through manual primary/secondary configuration and failover. Both solutions integrate MySQL Shell, Router, and automatic member provisioning for easy management.

Embed presentation

Downloaded 168 times
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Database Architectures Kenny Gryp MySQL Product Manager 1 / 28
2 / 282 / 28
  Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purpose 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 up in making purchasing decisions. The development, release and timing of any features or functionality described for Oracle´s product remains at the sole discretion of Oracle. 3 / 28
Past, Present & Future 4 / 28
Past, Present & Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 4 / 28
Past, Present & Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 2016-2019 - MySQL InnoDB Cluster Group Replication: Automatic membership changes, network partition handling, consistency... Shell to provide a powerful interface that helps in automating an integrating all components InnoDB CLONE to automatically provision members, fully integrated in InnoDB 4 / 28
Past, Present & Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 2016-2019 - MySQL InnoDB Cluster Group Replication: Automatic membership changes, network partition handling, consistency... Shell to provide a powerful interface that helps in automating an integrating all components InnoDB CLONE to automatically provision members, fully integrated in InnoDB 2020 - MySQL InnoDB Replicaset 'classic', 'asynchronous' Replication based Solution, fully integrated 4 / 28
MySQL InnoDB Cluster "A single product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
MySQL InnoDB Cluster "A single product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
Components: MySQL Server MySQL Group Replication MySQL Shell MySQL Router MySQL InnoDB Cluster "A single product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
One Product: MySQL All components developed together Integration of all components Full stack testing MySQL InnoDB Cluster - Goals 6 / 28
One Product: MySQL All components developed together Integration of all components Full stack testing Easy to Use One client: MySQL Shell Integrated orchestration Homogenous servers MySQL InnoDB Cluster - Goals 6 / 28
MySQL Group Replication 7 / 28
High Available Distributed MySQL DB Fault tolerance Automatic failover Active/Active update anywhere (limits apply) Automatic membership management Adding/removing members Network partitions, failures Conflict detection and resolution Prevents data loss MySQL Group Replication 7 / 28
MySQL Group Replication Implementation of Replicated Database State Machine Total Order - Writes XCOM - Paxos implementation Configurable Consistency Guarantees eventual consistency 8.0+: per session & global read/write consistency Using MySQL replication framework by design binary logs relay logs GTIDs: Global Transaction IDs Generally Available since MySQL 5.7 Supported on all platforms: linux, windows, solaris, macosx, freebsd 8 / 28
Recovery Time Objective (RTO) How fast should the service recover from a failure Recovery Point Objective (RPO) How much data loss can the service lose from a failure Business Requirements 9 / 28
Recovery Time Objective (RTO) How fast should the service recover from a failure Recovery Point Objective (RPO) How much data loss can the service lose from a failure Types of Failures High Availability: Single Server Failure, Network Partition Disaster Recovery: Full Region/Network Failure Human Error: Little Bobby Tables How Much None few seconds minutes hours day ... Business Requirements 9 / 28
Consistency: No Data Loss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) MySQL Group Replication - Use Cases 10 / 28
Consistency: No Data Loss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling MySQL Group Replication - Use Cases 10 / 28
Consistency: No Data Loss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling Read Scaleout Add/Remove members as needed Replication Lag handling with Flow Control Configurable Consistency Levels Eventual Full Consistency -- no stale reads MySQL Group Replication - Use Cases 10 / 28
Consistency: No Data Loss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling Read Scaleout Add/Remove members as needed Replication Lag handling with Flow Control Configurable Consistency Levels Eventual Full Consistency -- no stale reads Active/Active environments Write to many members at the same time ordered writes within the group (XCOM) guaranteed consistency Good write performance due to Optimistic Locking (workload dependent) MySQL Group Replication - Use Cases 10 / 28
MySQL Router 11 / 28
Transparent Access to Database Arch. "provide transparent routing between your application and back-end MySQL Servers" Transparent client connection routing Load balancing Application connection failover Little to no configuration needed Stateless design offers easy HA client routing Router as part of the application stack Integration into InnoDB Cluster & InnoDB ReplicaSet Understands Group Replication & Replication topology Currently TCP Port each for PRIMARY and NON-PRIMARY traffic MySQL Router 11 / 28
MySQL Shell 12 / 28
Database Administration Interface "MySQL Shell provides the developer and DBA with a single intuitive, flexible, and powerful interface for all MySQL related tasks!" Multi-Language: JavaScript, Python, and SQL Naturally scriptable Supports Document and Relational models Exposes full Development and Admin API Classic MySQL protocol and X protocol MySQL Shell 12 / 28
MySQL Shell - Easy to Use 13 / 28
MySQL InnoDB Cluster mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') MySQL Shell - Easy to Use 13 / 28
MySQL InnoDB Cluster mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') MySQL Shell - Easy to Use 13 / 28
MySQL InnoDB Cluster mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') Add server to the Cluster: mysql-js> cluster.addInstance('admin@mysql2') MySQL Shell - Easy to Use 13 / 28
MySQL InnoDB Cluster mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') Add server to the Cluster: mysql-js> cluster.addInstance('admin@mysql2') Bootstrap MySQL Router $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter MySQL Shell - Easy to Use 13 / 28
mysql-js> cluster.status() { "clusterName": "cluster", "defaultReplicaSet": { "name": "default", "primary": "mysql1:3306", "ssl": "REQUIRED", "status": "OK", "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", "topology": { "mysql1:3306": { "address": "mysql1:3306", "mode": "R/W", "readReplicas": {}, "role": "HA", "status": "ONLINE" }, "mysql2:3306": { "address": "mysql2:3306", "mode": "R/O", "readReplicas": {}, "role": "HA", "status": "ONLINE" }, "mysql3:3306": { "address": "mysql3:3306", "mode": "R/O", "readReplicas": {}, "role": "HA", "status": "ONLINE" } } } MySQL Shell - Easy to Use Check the Cluster status: 14 / 28
MySQL InnoDB Cluster - Evolving 15 / 28
Many of our customers have adopted InnoDB Cluster! Fully integrated MySQL Router Automatic Routing Ease of use with MySQL Shell Configuring, Adding, Removing members Group Replication Architecture Providing Consistency Automatic Failover Network Partition Handling No data loss in case of failure Automatic Member Provisioning (CLONE) MySQL InnoDB Cluster - Adoption 16 / 28
Introducing MySQL InnoDB ReplicaSet! 8.0.19 Feature! Fully integrated MySQL Router Automatic Routing Ease of use with MySQL Shell Configuring, Adding, Removing members Automatic Member Provisioning (CLONE) Replication Architecture: (manual) Switchover & Failover (asynchronous) Read Scaleout 'Simple' Replication architecture: no network/hardware requirements Providing Availability on PRIMARY when issues with secondaries or network MySQL InnoDB Replicaset 17 / 28
Past MySQL InnoDB ReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE MySQL InnoDB ReplicaSet - Features 18 / 28
Past MySQL InnoDB ReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication MySQL InnoDB ReplicaSet - Features 18 / 28
Past MySQL InnoDB ReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes MySQL InnoDB ReplicaSet - Features 18 / 28
Past MySQL InnoDB ReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes Manually or relying on external tools to make topology changes Easy to use manual switchover/failover MySQL InnoDB ReplicaSet - Features 18 / 28
Past MySQL InnoDB ReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes Manually or relying on external tools to make topology changes Easy to use manual switchover/failover Use additional monitoring tool log in on all machines to check topology status See status of the topology through MySQL Shell status() MySQL InnoDB ReplicaSet - Features 18 / 28
Past MySQL InnoDB ReplicaSet MySQL InnoDB ReplicaSet - Features 19 / 28
Past MySQL InnoDB ReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes MySQL InnoDB ReplicaSet - Features 19 / 28
Past MySQL InnoDB ReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle MySQL InnoDB ReplicaSet - Features 19 / 28
Past MySQL InnoDB ReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle A lot of manual steps and additional software required, always customized and often overengineered by MySQL DBA's Easy to use, even for MySQL beginner MySQL InnoDB ReplicaSet - Features 19 / 28
MySQL InnoDB ReplicaSet - Requirements & Limitations Requirements: MySQL 8 (SET PERSIST!) GTID Limitations: Manual failover No multi-primary as such topology cannot guarantee data consistency All secondary members replicate from primary 20 / 28
MySQL InnoDB ReplicaSet - Demo 00:00 21 / 28
MySQL InnoDB ReplicaSet - MySQL Router Integration --bootstrap to automatically configure Metadata schema contains Replication Topology Health checks are performed to all members Switchover to new primary (setPrimaryInstance()): Shell performs topology change, configures super_read_only and updates view_id in metadata Router automatically sees higher view_id and will redirect primary traffic to new primary When the Primary is lost: forcePrimaryInstance() Shell performs topology change, updates view_id in metadata and invalidates lost primary Router will notice topology change by higher view_id in metadata (if network allows) and automatically connect to new Primary 22 / 28
MySQL Shell - Easy to Use 23 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') MySQL Shell - Easy to Use 23 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') MySQL Shell - Easy to Use 23 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') Add server to the Cluster mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2') MySQL Shell - Easy to Use 23 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') Add server to the Cluster mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2') Bootstrap MySQL Router $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter MySQL Shell - Easy to Use Demo: https://mysqlserverteam.com/introducing-mysql-innodb-replicaset 23 / 28
By design chosen to be Manual failover Having external monitoring processes decide failover can cause a lot of false positives. External tool decides, if the tool has issues: even bigger issues. Split brain issues Majority of production deployments are configured with Manual Failover, which increases Uptime! When automatic failover is needed: use MySQL InnoDB Cluster instead of Semi-Sync MySQL InnoDB ReplicaSet - Manual Failover 24 / 28
Example: 1 Primary, 2 Secondaries, 2 Proxy hosts (App servers) 1 Management server: monitoring and making Topology changes automatically Problem: Management server & replica server is partitioned from all other servers What will happen? MySQL InnoDB ReplicaSet - Manual Failover 25 / 28
Example: 1 Primary, 2 Secondaries, 2 Proxy hosts (App servers) 1 Management server: monitoring and making Topology changes automatically Problem: Management server & replica server is partitioned from all other servers What will happen? The management host might promote the secondary causing split brain use MySQL InnoDB Cluster over Semi-Sync With semi-sync, all members have to ack (prevent split brain), causing downtime with every small glitch MySQL InnoDB ReplicaSet - Manual Failover 26 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members No data loss in case of member failure (Recovery Point Objective = 0 (RPO)) Consistency During planned switchover: No data loss, split brain is handled During manual Unplanned failover: up to user Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members No data loss in case of member failure (Recovery Point Objective = 0 (RPO)) Consistency During planned switchover: No data loss, split brain is handled During manual Unplanned failover: up to user Automatic Failover in case of failure (Easier to achieve a lower Recovery Time Objective (RTO) with stable network/servers) Manual switchover/failover only Which Solution fits me? 27 / 28
MySQL InnoDB Cluster MySQL InnoDB ReplicaSet Database Solutions http://www.mysql.com http://dev.mysql.com/doc http://www.mysqlhighavailability.com http://www.mysqlserverteam.com Kenny Gryp MySQL Product Manager 28 / 28

More Related Content

PDF
MySQL InnoDB Cluster - Group Replication
byFrederic Descamps
 
PDF
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
byMiguel Araújo
 
PDF
Inside MongoDB: the Internals of an Open-Source Database
byMike Dirolf
 
PDF
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11
byKenny Gryp
 
PDF
InnoDb Vs NDB Cluster
byMark Swarbrick
 
PDF
MySQL GTID Concepts, Implementation and troubleshooting
byMydbops
 
PDF
InnoDB Locking Explained with Stick Figures
byKarwin Software Solutions LLC
 
PDF
Wars of MySQL Cluster ( InnoDB Cluster VS Galera )
byMydbops
 
MySQL InnoDB Cluster - Group Replication
byFrederic Descamps
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
byMiguel Araújo
 
Inside MongoDB: the Internals of an Open-Source Database
byMike Dirolf
 
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11
byKenny Gryp
 
InnoDb Vs NDB Cluster
byMark Swarbrick
 
MySQL GTID Concepts, Implementation and troubleshooting
byMydbops
 
InnoDB Locking Explained with Stick Figures
byKarwin Software Solutions LLC
 
Wars of MySQL Cluster ( InnoDB Cluster VS Galera )
byMydbops
 

What's hot

PDF
MySQL InnoDB Cluster - New Features in 8.0 Releases - Best Practices
byKenny Gryp
 
PDF
MySQL InnoDB Cluster HA Overview & Demo
byKeith Hollman
 
PDF
MySQL InnoDB Cluster / ReplicaSet - Tutorial
byKenny Gryp
 
PDF
[2018] MySQL 이중화 진화기
byNHN FORWARD
 
PDF
MySQL InnoDB Cluster and Group Replication in a nutshell hands-on tutorial
byFrederic Descamps
 
PDF
MySQL InnoDB Cluster - Advanced Configuration & Operations
byFrederic Descamps
 
PDF
MySQL Advanced Administrator 2021 - 네오클로바
byNeoClova
 
PPTX
ProxySQL for MySQL
byMydbops
 
PPTX
MariaDB High Availability
byMariaDB plc
 
PDF
Almost Perfect Service Discovery and Failover with ProxySQL and Orchestrator
byJean-François Gagné
 
PDF
MySQL Parallel Replication: All the 5.7 and 8.0 Details (LOGICAL_CLOCK)
byJean-François Gagné
 
PPTX
My sql failover test using orchestrator
byYoungHeon (Roy) Kim
 
PPTX
Kafka 101
byClement Demonchy
 
PPTX
MariaDB Galera Cluster
byAbdul Manaf
 
ODP
MySQL Group Replication
byUlf Wendel
 
PDF
Kubernetes networking
bySim Janghoon
 
PDF
MariaDB 마이그레이션 - 네오클로바
byNeoClova
 
PDF
New features in ProxySQL 2.0 (updated to 2.0.9) by Rene Cannao (ProxySQL)
byAltinity Ltd
 
PDF
MariaDB Galera Cluster - Simple, Transparent, Highly Available
byMariaDB Corporation
 
PDF
Ansible Introduction
byRobert Reiz
 
MySQL InnoDB Cluster - New Features in 8.0 Releases - Best Practices
byKenny Gryp
 
MySQL InnoDB Cluster HA Overview & Demo
byKeith Hollman
 
MySQL InnoDB Cluster / ReplicaSet - Tutorial
byKenny Gryp
 
[2018] MySQL 이중화 진화기
byNHN FORWARD
 
MySQL InnoDB Cluster and Group Replication in a nutshell hands-on tutorial
byFrederic Descamps
 
MySQL InnoDB Cluster - Advanced Configuration & Operations
byFrederic Descamps
 
MySQL Advanced Administrator 2021 - 네오클로바
byNeoClova
 
ProxySQL for MySQL
byMydbops
 
MariaDB High Availability
byMariaDB plc
 
Almost Perfect Service Discovery and Failover with ProxySQL and Orchestrator
byJean-François Gagné
 
MySQL Parallel Replication: All the 5.7 and 8.0 Details (LOGICAL_CLOCK)
byJean-François Gagné
 
My sql failover test using orchestrator
byYoungHeon (Roy) Kim
 
Kafka 101
byClement Demonchy
 
MariaDB Galera Cluster
byAbdul Manaf
 
MySQL Group Replication
byUlf Wendel
 
Kubernetes networking
bySim Janghoon
 
MariaDB 마이그레이션 - 네오클로바
byNeoClova
 
New features in ProxySQL 2.0 (updated to 2.0.9) by Rene Cannao (ProxySQL)
byAltinity Ltd
 
MariaDB Galera Cluster - Simple, Transparent, Highly Available
byMariaDB Corporation
 
Ansible Introduction
byRobert Reiz
 

Similar to MySQL Database Architectures - InnoDB ReplicaSet & Cluster

PDF
MySQL Database Architectures - 2020-10
byKenny Gryp
 
PDF
MySQL InnoDB Cluster / ReplicaSet - Tutorial
byMiguel Araújo
 
PDF
20200613 my sql-ha-deployment
byIvan Ma
 
PDF
20190817 coscup-oracle my sql innodb cluster sharing
byIvan Ma
 
PDF
MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore
bySujatha Sivakumar
 
PDF
MySQL Day Paris 2016 - MySQL HA: InnoDB Cluster and NDB Cluster
byOlivier DASINI
 
PDF
How to operate MySQL InnoDB Cluster with MySQL Shell
byFrederic Descamps
 
PDF
20191001 bkk-secret-of inno-db_clusterv1
byIvan Ma
 
PDF
MySQL InnoDB Cluster and NDB Cluster
byMario Beck
 
PDF
MySQL 8.0 InnoDB Cluster - Easiest Tutorial
byFrederic Descamps
 
PDF
MySQL Database Architectures - 2022-08
byKenny Gryp
 
PDF
MySQL InnoDB Cluster and MySQL Group Replication @HKOSC 2017
byIvan Ma
 
PDF
Another MySQL HA Solution for ProxySQL Users, Easy and All Integrated: MySQL ...
byFrederic Descamps
 
PDF
MySQL InnoDB Cluster: High Availability Made Easy!
byVittorio Cioe
 
PDF
Buytaert kris my_sql-pacemaker
bykuchinskaya
 
PDF
Confoo 202 - MySQL Group Replication and ReplicaSet
byDave Stokes
 
PDF
MySQL Database Architectures - High Availability and Disaster Recovery Solution
byMiguel Araújo
 
PDF
Introduction to MySQL InnoDB Cluster
byFrederic Descamps
 
PDF
MySQL High Availability -- InnoDB Clusters
byMatt Lord
 
PDF
Sunshine php my sql 8.0 v2
byKathy Forte (Hassard)
 
MySQL Database Architectures - 2020-10
byKenny Gryp
 
MySQL InnoDB Cluster / ReplicaSet - Tutorial
byMiguel Araújo
 
20200613 my sql-ha-deployment
byIvan Ma
 
20190817 coscup-oracle my sql innodb cluster sharing
byIvan Ma
 
MySQL InnoDB Cluster and Group Replication - OSI 2017 Bangalore
bySujatha Sivakumar
 
MySQL Day Paris 2016 - MySQL HA: InnoDB Cluster and NDB Cluster
byOlivier DASINI
 
How to operate MySQL InnoDB Cluster with MySQL Shell
byFrederic Descamps
 
20191001 bkk-secret-of inno-db_clusterv1
byIvan Ma
 
MySQL InnoDB Cluster and NDB Cluster
byMario Beck
 
MySQL 8.0 InnoDB Cluster - Easiest Tutorial
byFrederic Descamps
 
MySQL Database Architectures - 2022-08
byKenny Gryp
 
MySQL InnoDB Cluster and MySQL Group Replication @HKOSC 2017
byIvan Ma
 
Another MySQL HA Solution for ProxySQL Users, Easy and All Integrated: MySQL ...
byFrederic Descamps
 
MySQL InnoDB Cluster: High Availability Made Easy!
byVittorio Cioe
 
Buytaert kris my_sql-pacemaker
bykuchinskaya
 
Confoo 202 - MySQL Group Replication and ReplicaSet
byDave Stokes
 
MySQL Database Architectures - High Availability and Disaster Recovery Solution
byMiguel Araújo
 
Introduction to MySQL InnoDB Cluster
byFrederic Descamps
 
MySQL High Availability -- InnoDB Clusters
byMatt Lord
 
Sunshine php my sql 8.0 v2
byKathy Forte (Hassard)
 

More from Kenny Gryp

PDF
MySQL Operator for Kubernetes
byKenny Gryp
 
PDF
MySQL Connectors 8.0.19 & DNS SRV
byKenny Gryp
 
PDF
MySQL Group Replication - Ready For Production? (2018-04)
byKenny Gryp
 
PDF
Reducing Risk When Upgrading MySQL
byKenny Gryp
 
PDF
Percona XtraDB Cluster vs Galera Cluster vs MySQL Group Replication
byKenny Gryp
 
PDF
MySQL Group Replication
byKenny Gryp
 
PDF
Multi Source Replication With MySQL 5.7 @ Verisure
byKenny Gryp
 
PDF
MySQL Group Replication - HandsOn Tutorial
byKenny Gryp
 
PDF
Online MySQL Backups with Percona XtraBackup
byKenny Gryp
 
PDF
Advanced Percona XtraDB Cluster in a nutshell... la suite
byKenny Gryp
 
PDF
Java MySQL Connector & Connection Pool Features & Optimization
byKenny Gryp
 
PDF
Percona XtraDB Cluster
byKenny Gryp
 
MySQL Operator for Kubernetes
byKenny Gryp
 
MySQL Connectors 8.0.19 & DNS SRV
byKenny Gryp
 
MySQL Group Replication - Ready For Production? (2018-04)
byKenny Gryp
 
Reducing Risk When Upgrading MySQL
byKenny Gryp
 
Percona XtraDB Cluster vs Galera Cluster vs MySQL Group Replication
byKenny Gryp
 
MySQL Group Replication
byKenny Gryp
 
Multi Source Replication With MySQL 5.7 @ Verisure
byKenny Gryp
 
MySQL Group Replication - HandsOn Tutorial
byKenny Gryp
 
Online MySQL Backups with Percona XtraBackup
byKenny Gryp
 
Advanced Percona XtraDB Cluster in a nutshell... la suite
byKenny Gryp
 
Java MySQL Connector & Connection Pool Features & Optimization
byKenny Gryp
 
Percona XtraDB Cluster
byKenny Gryp
 

Recently uploaded

PDF
谷歌留痕技术教程[ 𝙩𝙤𝙥 𝟮𝟯𝟯. 𝙘 𝙤𝙢 ]
by6stynggfo
 
PDF
Physiotherapist App Development for Modern Rehabilitation
byV3CUBE TECHNOLABS
 
PDF
SLIDE PROPARTNER SUMMIT 2025 - ITALY.pdf
bygiuo
 
PDF
LogiNext Media Kit & Company Overview 2025
bysmritipatil055
 
DOCX
The Rise of Headless CMS in Modern Web Development.docx
bywork4noahmiller
 
PDF
Water Delivery App Development Solutions.pdf
byeSiteWorld TechnoLabs Pvt. Ltd.
 
PDF
Figma systems development services
bydavidjohansen1597
 
PPTX
Windows File System Monitoring Tool Using C and C++
byAkshay Muley
 
PDF
AI-native development: from Prompt to Platform
byMaxim Salnikov
 
PPTX
Applicius Technologies: Full Service Overview for Branding, SEO, Web & App De...
byappliciustech
 
PDF
Smart ways to se AI in your business , presentation
byAI n Dot Net
 
PDF
LogiNext Media Kit & Company Overview 2025
bydhrutipatelk5617
 
PDF
Own Your Domain Before It Owns You - Domain Driven Design for Pragmaticians
byPosedio GmbH
 
PDF
LogiNext Media Kit & Company Overview 2025
bypriyajoshi2929
 
PDF
LogiNext Media Kit & Company Overview 2025
bysanikaroy72
 
PDF
Why I Volunteer at FOSDEM and You Should Too
byImma Valls Bernaus
 
PDF
LogiNext Media Kit & Company Overview 2025
byswatishahz9031
 
PDF
GDG ON CAMPUS NETAJI SUBHASH ENGINEERING COLLEGE BUILDING INTELLIGENT WEB APP...
bydscnsecorg
 
PDF
Accelerating Data Validation with QuerySurge AI
byRTTS
 
PDF
LogiNext Media Kit & Company Overview 2025
bynidhisharmaq7184
 
谷歌留痕技术教程[ 𝙩𝙤𝙥 𝟮𝟯𝟯. 𝙘 𝙤𝙢 ]
by6stynggfo
 
Physiotherapist App Development for Modern Rehabilitation
byV3CUBE TECHNOLABS
 
SLIDE PROPARTNER SUMMIT 2025 - ITALY.pdf
bygiuo
 
LogiNext Media Kit & Company Overview 2025
bysmritipatil055
 
The Rise of Headless CMS in Modern Web Development.docx
bywork4noahmiller
 
Water Delivery App Development Solutions.pdf
byeSiteWorld TechnoLabs Pvt. Ltd.
 
Figma systems development services
bydavidjohansen1597
 
Windows File System Monitoring Tool Using C and C++
byAkshay Muley
 
AI-native development: from Prompt to Platform
byMaxim Salnikov
 
Applicius Technologies: Full Service Overview for Branding, SEO, Web & App De...
byappliciustech
 
Smart ways to se AI in your business , presentation
byAI n Dot Net
 
LogiNext Media Kit & Company Overview 2025
bydhrutipatelk5617
 
Own Your Domain Before It Owns You - Domain Driven Design for Pragmaticians
byPosedio GmbH
 
LogiNext Media Kit & Company Overview 2025
bypriyajoshi2929
 
LogiNext Media Kit & Company Overview 2025
bysanikaroy72
 
Why I Volunteer at FOSDEM and You Should Too
byImma Valls Bernaus
 
LogiNext Media Kit & Company Overview 2025
byswatishahz9031
 
GDG ON CAMPUS NETAJI SUBHASH ENGINEERING COLLEGE BUILDING INTELLIGENT WEB APP...
bydscnsecorg
 
Accelerating Data Validation with QuerySurge AI
byRTTS
 
LogiNext Media Kit & Company Overview 2025
bynidhisharmaq7184
 

MySQL Database Architectures - InnoDB ReplicaSet & Cluster

  • 1.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Database Architectures Kenny Gryp MySQL Product Manager 1 / 28
  • 2.
    2 / 282/ 28
  • 3.
      Safe Harbor Statement Thefollowing is intended to outline our general product direction. It is intended for information purpose 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 up in making purchasing decisions. The development, release and timing of any features or functionality described for Oracle´s product remains at the sole discretion of Oracle. 3 / 28
  • 4.
    Past, Present &Future 4 / 28
  • 5.
    Past, Present &Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 4 / 28
  • 6.
    Past, Present &Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 2016-2019 - MySQL InnoDB Cluster Group Replication: Automatic membership changes, network partition handling, consistency... Shell to provide a powerful interface that helps in automating an integrating all components InnoDB CLONE to automatically provision members, fully integrated in InnoDB 4 / 28
  • 7.
    Past, Present &Future In The Past - MANUAL Setting up Replication topology was done manually, taking many steps including user management, restoring backups, configuring replication... MySQL offered the technical pieces, leaving it up to the user to setup an (always customized) architecture This requires technical components ... bringing lot's of work for DBA's and experts, who spent their time automating 2016-2019 - MySQL InnoDB Cluster Group Replication: Automatic membership changes, network partition handling, consistency... Shell to provide a powerful interface that helps in automating an integrating all components InnoDB CLONE to automatically provision members, fully integrated in InnoDB 2020 - MySQL InnoDB Replicaset 'classic', 'asynchronous' Replication based Solution, fully integrated 4 / 28
  • 8.
    MySQL InnoDB Cluster "Asingle product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
  • 9.
    MySQL InnoDB Cluster "Asingle product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
  • 10.
    Components: MySQL Server MySQL GroupReplication MySQL Shell MySQL Router MySQL InnoDB Cluster "A single product — MySQL — with high availability and scaling features baked in; providing an integrated end-to-end solution that is easy to use." 5 / 28
  • 11.
    One Product: MySQL Allcomponents developed together Integration of all components Full stack testing MySQL InnoDB Cluster - Goals 6 / 28
  • 12.
    One Product: MySQL Allcomponents developed together Integration of all components Full stack testing Easy to Use One client: MySQL Shell Integrated orchestration Homogenous servers MySQL InnoDB Cluster - Goals 6 / 28
  • 13.
  • 14.
    High Available DistributedMySQL DB Fault tolerance Automatic failover Active/Active update anywhere (limits apply) Automatic membership management Adding/removing members Network partitions, failures Conflict detection and resolution Prevents data loss MySQL Group Replication 7 / 28
  • 15.
    MySQL Group Replication Implementationof Replicated Database State Machine Total Order - Writes XCOM - Paxos implementation Configurable Consistency Guarantees eventual consistency 8.0+: per session & global read/write consistency Using MySQL replication framework by design binary logs relay logs GTIDs: Global Transaction IDs Generally Available since MySQL 5.7 Supported on all platforms: linux, windows, solaris, macosx, freebsd 8 / 28
  • 16.
    Recovery Time Objective(RTO) How fast should the service recover from a failure Recovery Point Objective (RPO) How much data loss can the service lose from a failure Business Requirements 9 / 28
  • 17.
    Recovery Time Objective(RTO) How fast should the service recover from a failure Recovery Point Objective (RPO) How much data loss can the service lose from a failure Types of Failures High Availability: Single Server Failure, Network Partition Disaster Recovery: Full Region/Network Failure Human Error: Little Bobby Tables How Much None few seconds minutes hours day ... Business Requirements 9 / 28
  • 18.
    Consistency: No DataLoss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) MySQL Group Replication - Use Cases 10 / 28
  • 19.
    Consistency: No DataLoss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling MySQL Group Replication - Use Cases 10 / 28
  • 20.
    Consistency: No DataLoss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling Read Scaleout Add/Remove members as needed Replication Lag handling with Flow Control Configurable Consistency Levels Eventual Full Consistency -- no stale reads MySQL Group Replication - Use Cases 10 / 28
  • 21.
    Consistency: No DataLoss (RPO=0) in event of failure of (primary) member Split brain prevention (Quorum) Highly Available: Automatic Failover Primary members are automatically elected Automatic Network Partition handling Read Scaleout Add/Remove members as needed Replication Lag handling with Flow Control Configurable Consistency Levels Eventual Full Consistency -- no stale reads Active/Active environments Write to many members at the same time ordered writes within the group (XCOM) guaranteed consistency Good write performance due to Optimistic Locking (workload dependent) MySQL Group Replication - Use Cases 10 / 28
  • 22.
  • 23.
    Transparent Access toDatabase Arch. "provide transparent routing between your application and back-end MySQL Servers" Transparent client connection routing Load balancing Application connection failover Little to no configuration needed Stateless design offers easy HA client routing Router as part of the application stack Integration into InnoDB Cluster & InnoDB ReplicaSet Understands Group Replication & Replication topology Currently TCP Port each for PRIMARY and NON-PRIMARY traffic MySQL Router 11 / 28
  • 24.
  • 25.
    Database Administration Interface "MySQLShell provides the developer and DBA with a single intuitive, flexible, and powerful interface for all MySQL related tasks!" Multi-Language: JavaScript, Python, and SQL Naturally scriptable Supports Document and Relational models Exposes full Development and Admin API Classic MySQL protocol and X protocol MySQL Shell 12 / 28
  • 26.
    MySQL Shell -Easy to Use 13 / 28
  • 27.
    MySQL InnoDB Cluster mysql-js>c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') MySQL Shell - Easy to Use 13 / 28
  • 28.
    MySQL InnoDB Cluster mysql-js>c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') MySQL Shell - Easy to Use 13 / 28
  • 29.
    MySQL InnoDB Cluster mysql-js>c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') Add server to the Cluster: mysql-js> cluster.addInstance('admin@mysql2') MySQL Shell - Easy to Use 13 / 28
  • 30.
    MySQL InnoDB Cluster mysql-js>c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') Configure server to add later: mysql-js> dba.con gureInstance('admin@mysql2') Add server to the Cluster: mysql-js> cluster.addInstance('admin@mysql2') Bootstrap MySQL Router $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter MySQL Shell - Easy to Use 13 / 28
  • 31.
    mysql-js> cluster.status() { "clusterName": "cluster", "defaultReplicaSet":{ "name": "default", "primary": "mysql1:3306", "ssl": "REQUIRED", "status": "OK", "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", "topology": { "mysql1:3306": { "address": "mysql1:3306", "mode": "R/W", "readReplicas": {}, "role": "HA", "status": "ONLINE" }, "mysql2:3306": { "address": "mysql2:3306", "mode": "R/O", "readReplicas": {}, "role": "HA", "status": "ONLINE" }, "mysql3:3306": { "address": "mysql3:3306", "mode": "R/O", "readReplicas": {}, "role": "HA", "status": "ONLINE" } } } MySQL Shell - Easy to Use Check the Cluster status: 14 / 28
  • 32.
    MySQL InnoDB Cluster- Evolving 15 / 28
  • 33.
    Many of ourcustomers have adopted InnoDB Cluster! Fully integrated MySQL Router Automatic Routing Ease of use with MySQL Shell Configuring, Adding, Removing members Group Replication Architecture Providing Consistency Automatic Failover Network Partition Handling No data loss in case of failure Automatic Member Provisioning (CLONE) MySQL InnoDB Cluster - Adoption 16 / 28
  • 34.
    Introducing MySQL InnoDBReplicaSet! 8.0.19 Feature! Fully integrated MySQL Router Automatic Routing Ease of use with MySQL Shell Configuring, Adding, Removing members Automatic Member Provisioning (CLONE) Replication Architecture: (manual) Switchover & Failover (asynchronous) Read Scaleout 'Simple' Replication architecture: no network/hardware requirements Providing Availability on PRIMARY when issues with secondaries or network MySQL InnoDB Replicaset 17 / 28
  • 35.
    Past MySQL InnoDBReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE MySQL InnoDB ReplicaSet - Features 18 / 28
  • 36.
    Past MySQL InnoDBReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication MySQL InnoDB ReplicaSet - Features 18 / 28
  • 37.
    Past MySQL InnoDBReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes MySQL InnoDB ReplicaSet - Features 18 / 28
  • 38.
    Past MySQL InnoDBReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes Manually or relying on external tools to make topology changes Easy to use manual switchover/failover MySQL InnoDB ReplicaSet - Features 18 / 28
  • 39.
    Past MySQL InnoDBReplicaSet Restore a backup to provision a member Automatically provisioning new members: InnoDB CLONE Configure Replication Users Configure Replication MySQL Shell Automatically configures users & replication Manually configuring, adding removing servers in Application, MySQL Router (or other proxy) Integrated MySQL Router load balancing Only need to bootstrap Router Router is stateless, adapts to topology changes Manually or relying on external tools to make topology changes Easy to use manual switchover/failover Use additional monitoring tool log in on all machines to check topology status See status of the topology through MySQL Shell status() MySQL InnoDB ReplicaSet - Features 18 / 28
  • 40.
    Past MySQL InnoDBReplicaSet MySQL InnoDB ReplicaSet - Features 19 / 28
  • 41.
    Past MySQL InnoDBReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes MySQL InnoDB ReplicaSet - Features 19 / 28
  • 42.
    Past MySQL InnoDBReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle MySQL InnoDB ReplicaSet - Features 19 / 28
  • 43.
    Past MySQL InnoDBReplicaSet complexity: user is responsible for the full configuration of every component and it's settings Shell configures Server, Router, Replication in a standardized best practice setup, prevents mistakes every setup is a customized setup Standard Solution -- Supported & QA'ed by Oracle A lot of manual steps and additional software required, always customized and often overengineered by MySQL DBA's Easy to use, even for MySQL beginner MySQL InnoDB ReplicaSet - Features 19 / 28
  • 44.
    MySQL InnoDB ReplicaSet- Requirements & Limitations Requirements: MySQL 8 (SET PERSIST!) GTID Limitations: Manual failover No multi-primary as such topology cannot guarantee data consistency All secondary members replicate from primary 20 / 28
  • 45.
    MySQL InnoDB ReplicaSet- Demo 00:00 21 / 28
  • 46.
    MySQL InnoDB ReplicaSet- MySQL Router Integration --bootstrap to automatically configure Metadata schema contains Replication Topology Health checks are performed to all members Switchover to new primary (setPrimaryInstance()): Shell performs topology change, configures super_read_only and updates view_id in metadata Router automatically sees higher view_id and will redirect primary traffic to new primary When the Primary is lost: forcePrimaryInstance() Shell performs topology change, updates view_id in metadata and invalidates lost primary Router will notice topology change by higher view_id in metadata (if network allows) and automatically connect to new Primary 22 / 28
  • 47.
    MySQL Shell -Easy to Use 23 / 28
  • 48.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') MySQL Shell - Easy to Use 23 / 28
  • 49.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') MySQL Shell - Easy to Use 23 / 28
  • 50.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') Add server to the Cluster mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2') MySQL Shell - Easy to Use 23 / 28
  • 51.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet mysql-js> c admin@mysql1 mysql-js> cluster = dba.createCluster('cluster') mysql-js> c admin@mysql1 mysql-js> rs = dba.createReplicaSet('replicaset') Configure server to add later mysql-js> dba.con gureInstance('admin@mysql2') mysql-js> dba.con gureReplicaSetInstance('admin@mysql2') Add server to the Cluster mysql-js> cluster.addInstance('admin@mysql2') mysql-js> rs.addInstance('admin@mysql2') Bootstrap MySQL Router $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter $ sudo mysqlrouter --user=mysqlrouter --bootstrap $ sudo systemctl start mysqlrouter MySQL Shell - Easy to Use Demo: https://mysqlserverteam.com/introducing-mysql-innodb-replicaset 23 / 28
  • 52.
    By design chosento be Manual failover Having external monitoring processes decide failover can cause a lot of false positives. External tool decides, if the tool has issues: even bigger issues. Split brain issues Majority of production deployments are configured with Manual Failover, which increases Uptime! When automatic failover is needed: use MySQL InnoDB Cluster instead of Semi-Sync MySQL InnoDB ReplicaSet - Manual Failover 24 / 28
  • 53.
    Example: 1 Primary, 2Secondaries, 2 Proxy hosts (App servers) 1 Management server: monitoring and making Topology changes automatically Problem: Management server & replica server is partitioned from all other servers What will happen? MySQL InnoDB ReplicaSet - Manual Failover 25 / 28
  • 54.
    Example: 1 Primary, 2Secondaries, 2 Proxy hosts (App servers) 1 Management server: monitoring and making Topology changes automatically Problem: Management server & replica server is partitioned from all other servers What will happen? The management host might promote the secondary causing split brain use MySQL InnoDB Cluster over Semi-Sync With semi-sync, all members have to ack (prevent split brain), causing downtime with every small glitch MySQL InnoDB ReplicaSet - Manual Failover 26 / 28
  • 55.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Which Solution fits me? 27 / 28
  • 56.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Which Solution fits me? 27 / 28
  • 57.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads Which Solution fits me? 27 / 28
  • 58.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Which Solution fits me? 27 / 28
  • 59.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members Which Solution fits me? 27 / 28
  • 60.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members No data loss in case of member failure (Recovery Point Objective = 0 (RPO)) Consistency During planned switchover: No data loss, split brain is handled During manual Unplanned failover: up to user Which Solution fits me? 27 / 28
  • 61.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Single Primary, multiple Secondaries Multi Primary mode (write to all) Single Primary, multiple Secondaries Read Scaleout with configurable consistent reads Read Scaleout with stale reads All members partake in consensus (write performance is as fast as it's slowest node) Secondary members only get stream of changes (binlog), does not impact Primary Stable network is required: Network glitches cause stalls/membership changes Uneven amount of members (3-5) No network requirements: glitches in network do not impact availability 2 or more members No data loss in case of member failure (Recovery Point Objective = 0 (RPO)) Consistency During planned switchover: No data loss, split brain is handled During manual Unplanned failover: up to user Automatic Failover in case of failure (Easier to achieve a lower Recovery Time Objective (RTO) with stable network/servers) Manual switchover/failover only Which Solution fits me? 27 / 28
  • 62.
    MySQL InnoDB ClusterMySQL InnoDB ReplicaSet Database Solutions http://www.mysql.com http://dev.mysql.com/doc http://www.mysqlhighavailability.com http://www.mysqlserverteam.com Kenny Gryp MySQL Product Manager 28 / 28