The document discusses a webinar on MySQL group replication held on February 1, 2017, covering various aspects of high availability (HA) and application modernization. It explains MySQL replication technologies, emphasizing the significance of MySQL group replication, its functionality, requirements, and the overarching principles of maintaining high availability. Key highlights include the automation of server fail-overs and conflict handling, which contribute to a fault-tolerant and highly available replicated database system.

1. WEBINAR
on
MySQL Group Replication
1st Feb 2017 between 5 -6 pm IST
Delhi, India

2. 2
EXPERIENCE
Systems of Engagement
DIGITIZATION
CUSTOMER
Propelling the enterprise into the new world
ENTERPRISE
EFFICIENCY
Systems of Records
MODERNIZATION
For a seamless tomorrow

3. 3 © OSSCUBE 2017. All Rights Reserved.33/28/2017
Digital :Delivering an unparalleled customer experience
Customer Commerce Operations
Operational Efficiency
Collaboration
Insights & Visibility
Superior Customer
Experience
Product Information
Management
Digital User
Experience
Digital Asset
Management
Analytics
E-Commerce
Enterprise Mobility
Solutions
WCM
Omni Channel
Integration
CRM & Marketing
Automation
Customer
Engagement
Limited Data Insights
High Costs & Risks
(Low Process
Visibility)
Low Business Agility
Inconsistent
Customer
Experience
Legacy Systems
New Age Technology
Adoption
Customer First CX
System Flexibility &
Scalability
Seamless Cross Channel
(Mobile, Offline, Omni
Channel) Integration
Maximize Global Sales
Lower Costs

4. 4
Modernizing legacy systems
Application
Modernization
Architecture Cloud
Mobile App
ETL/Data Transformation
Enterprise
Open Source
Eliminate
Automate
Lean
AnalyzeOptimize
STANDARDIZATION
DIGITAL READY
FLEXIBILITY
SAAS/CLOUD
LOW BUSINESS AGILITY
HIGH OPERATIONAL COSTS
COMPLEXITY IN TECH
LANDSCAPE
SKILL NON-AVAILABILITY
© OSSCUBE 2017. All Rights Reserved.43/28/2017

5. 28 March 2017 © OSSCube 2016. All Rights Reserved. 5
High Availability
Group Replication Basics
Group Replication installation, configuration and deployment
Group Replication Troubleshooting

6. 28 March 2017 © OSSCube 2016. All Rights Reserved. 6
High Availability

7. 28 March 2017 © OSSCube 2016. All Rights Reserved. 7
High Availability
• Principles of High Availability
 Elimination of single points of failure
 Reliable crossover. In multi threaded systems, the crossover point itself tends to become a single point
of failure
 Detection of failures as they occur. If the two principles above are observed, then a user may never
see a failure. But the maintenance activity must
• Causes of loosing HA
 Failures of hosts , Databases / MySQL
 Operating system
 The hardware
 Maintenance activity that may otherwise cause downtime
 And many more ……

8. 28 March 2017 © OSSCube 2017. All Rights Reserved. 8
MySQL HA Solutions
• HA is achieved via redundancy
• The primary solutions supported by MySQL include:
 MySQL Native Replication
 MySQL Cluster
 MySQL with DRBD
 Galera Cluster
 MySQL Group Replication

9. 28 March 2017 © OSSCube 2017. All Rights Reserved. 9
Replication Technologies
• Primary-Secondary Replication
 MySQL Asynchronous Replication
 MySQL Semi-synchronous Replication
• Group Replication

10. 28 March 2017 © OSSCube 2017. All Rights Reserved. 10
MySQL Asynchronous Replication

11. 28 March 2017 © OSSCube 2017. All Rights Reserved. 11
MySQL Semi-synchronous Replication

12. 28 March 2017 © OSSCube 2017. All Rights Reserved. 12
MySQL Group Replication
• What is MySQL Group Replication ?
Update everywhere replication plugin for MySQL with built-in automatic distributed recovery,
conflict handling, group membership and distributed agreement.
• What does the MySQL Group Replication plugin do for the user
 Removes the need for handling server fail-over.
 Provides fault tolerance.
 Enables update everywhere setups.
 Automates group reconfiguration (handling of crashes, failures, re-connects).
 Provides a highly available replicated database.
 Automatic distributed coordination (protects against split-brain and message loss).
 The number of servers (n) needed to tolerate f failures is based on formula n = 2 x f + 1.

13. 28 March 2017 © OSSCube 2017. All Rights Reserved. 13
MySQL Group Replication

14. 28 March 2017 © OSSCube 2017. All Rights Reserved. 14
MySQL Group Replication

15. 28 March 2017 © OSSCube 2017. All Rights Reserved. 15
MySQL Group Replication Requirements
• Infrastructure
 Data must be stored in the transactional storage engine InnoDB
 Every table must have a primary key
 IPv4 network
 Low latency, high bandwidth network
 Up to 9 servers in the group
• Configuration
 Binary Log must be active
 Binary Log Format must be set to ROW
 Global Transaction Identifiers must be turned on
 Replication applier needs to have replication metadata repositories stored in system tables
 Transaction write set extraction must be enabled
 Servers need to log binary logs that are applied through the replication applier

16. 28 March 2017 © OSSCube 2017. All Rights Reserved. 16
Plugin Architecture
• Built on top of proven technology!
 Shares much of MySQL Replication infrastructure thence does not feel alien!
Multi-Master approach to replication.
• Built on reusable components!
 Layered implementation approach.
 Interface driven development.
 Decoupled from the server core.
 The plugin registers as listener to server events.
 Reuses the capture procedure from regular replication.
 Provides further decoupling from the communication infrastructure.

17. 28 March 2017 © OSSCube 2017. All Rights Reserved. 17
Plugin Architecture

18. 28 March 2017 © OSSCube 2017. All Rights Reserved. 18
DEMO
DEMO

19. 28 March 2017 © OSSCube 2017. All Rights Reserved. 19
Q&A
Q&A

20. 28 March 2017 © OSSCube 2016. All Rights Reserved. 20