Event: Mywebinar (Mydbops) Topic: High Availability with InnoDB Cluster (This presentation deals with the transaction flow in InnoDB Cluster and how it can be deployed on a WAN based network for High Availability.) Presenter: Karthik P R (Founder / CEO - Mydbops )

1. High Availability With InnoDB
Clusters
Karthik P R
CEO, Mydbops
January 09, 2020
Mydbops webinar

2. Interested in Open Source Database technologies
11 Years of Experience with MySQL
Ex-Yahoo!
Tech Speaker/ Blogger
CEO Mydbops
Karthik P R
About Me

3. Database
Consulting
Services
Managed
Database
Services
Focuses on Top Opensource database MySQL,MariaDB,
MongoDB and PostgreSQL ON Premises and Cloud
Mydbops Services

4. Database Engineer
Database Administrator
Database Reliability Engineers
Cloud DBA
Devops Engineer
SRE's
Audience

5. MySQL High Availability
Solution Overview

6. Replication ( redundancy ) is a common solution for High Availability
MySQL Replication
Native Replication ( Async Replication )
Source - Source / Source - Replica
Cascaded Replication
Group Replication ( Sync Replication )
Availability of the database systems Matters
MySQL High Availability Solution Overview

7. InnoDB Cluster is a combination of multiple MySQL Products
MySQL Shell
MySQL Router
MySQL Servers With Group Replication
InnoDB Cluster

8. InnoDB Cluster and its Components
MySQL
Shell
MySQL
Router
MySQL
Servers
(with GR)

9. InnoDB Cluster

10. Synchronous Replication ( Eventually )
Single Primary / Multi Primary modes
Optimistic Transaction Locking
Group Membership Service
Transaction ordering
Group communication system ( Consensus )
InnoDB Cluster

11. Paxos based Consensus ( XCOM ).
Supports only InnoDB Engine.
Software-based Replication ( Database state machine )
Binary log-based replication.
Ideal for OLTP workload.
Support all platforms as MySQL Server.
InnoDB Cluster

12. Transaction in Group Replication

13. Transaction follow 2P commit
Voting Phase
Commit Phase
Allow Multo writer mode
Quorum has to be maintained
N= ( 2F + 1 )
Transaction in Group Replictaion

14. Commit Locally
Write Set
Conflict Detection
Apply
Y Rollback
Receiver node writes

15. The Transaction is originated in Primary (leader) and request a Commit.
The Transaction ( write set ) is distributed
Certification is made on nodes
Applied to the nodes ( Relay log )
Send the acknowledgment back to the Primary ( leader )
Transaction in Group Replictaion

16. Transaction in Group Replictaion

17. Flow control kick in when the applier lag beyond the threshold
The consistency is controlled by Flow control
The default is the Quota Mode
Flow control throttle the writes once activated
Consistency at reads and writes can be controlled by
group_replication_consistency
Transaction in Group Replictaion

18. The tuning for InnoDB and Replication applies
Global Memory
group_replication_message_cache_size
Message Compression and Binlog Compression ( N/W Saturation )
Message Fragmentation ( Huge transactions )
Group Replication Tuning

19. Single Primary Writes
Avoid huge transactions.
Stable N/W system
Better and more stable with MySQL 8.0
Use it with a Load balancer like ProxySQL or Router
Best Practices

20. Reach Us : Info@mydbops.com
Thank You