Replication latest features: the community sceptic roundup

on YouTube ↗51m

" summary

Coverage of GTID, multi‑source, parallel appliers and group replication focuses on concrete behavior and monitoring: MySQL uses UUID GTIDs and leaves GTIDs off by default while MariaDB uses domain/server/number GTIDs that are human‑readable and enables them; Performance Schema and MySQL/MariaDB replication tables split received vs executed info so full state often requires showslave status; parallel apply improves from schema‑based (5.6) to logical clock (5.7/8) but cannot be toggled per channel in multissource; group replication uses a cluster‑wide GTID and synchronous distribution but asynchronous execution, causing possible rollbacks on conflicts.

AI-written summary · about

" chapters (38)

1. 0:00About me Who's this guy?
2. 1:58Actors We will see practical examples with the following systems
3. 2:16Focus on monitoring The most important reason
4. 2:59Transactions blues You think you know where your transactions are ... until something unexpected happens
5. 3:33Transaction problem in a nutshell (1)
6. 4:12Transaction problem with GTID (1)
7. 4:43MySQL 5.6 & 5.7 A half baked feature, which kind of works
8. 7:38MySQL 5.7: What you see in the master
9. 8:43MySQL 5.7: What you see in the slave
10. 10:10MariaDB 10 A well thought feature, with some questionable choices
11. 11:25MariaDB 10.0: What you see in the master
12. 11:57MariaDB 10.0: What you see in the slave
13. 13:48Sceptic assessment global transaction identifiers
14. 14:49MySQL 5.6 crash-safe tables There are tables that can replace files, and SHOW statements .... up to a point
15. 15:36MySQL tables Very detailed, but designed in different stages
16. 16:37MySQL 5.7 additional tables in the slave Performance Schema helps with monitoring
17. 17:49MySQL 8.0.1 addition Some good news
18. 18:22MariaDB 10 crash-safe tables A complete redesign of the monitoring system, integrated with GTID
19. 18:57MySQL 5.7: tables in the slave
20. 20:52MySQL 8.0.1: tables in the slave
21. 21:32Sceptic assessment: monitoring in crash-safe tables
22. 23:01What is it? The dream of every DBA is to have a group of database servers that behave like a single server
23. 23:36Implementation (1) MySQL 5.7 Introduced in MySQL 5.7.7
24. 24:21MySQL 5.7 example Setting several channels CHANGE MASTER TO
25. 25:10MariaDB 10.1 example Setting several channels
26. 26:48Multi-source replication monitoring
27. 29:28Sceptic assessment: Multi source replication
28. 30:19MySQL multi-source issues
29. 30:52MariaDB multi-source issues
30. 31:40Parallel apply When the slave lags, using parallel threads may speed up things
31. 32:39Single vs parallel
32. 33:47Implementation (1) Tungsten Replicator The granddaddy of parallel replication, happily deployed in production for years
33. 36:20MariaDB 10 The latest contender
34. 36:56New development in MariaDB 10.1 A new algorithm for parallel replication
35. 37:29Sceptic assessment: parallel replication
36. 38:43Group replication New in MySQL 5.7.17+ and 8.0.1
37. 39:41Principles Many changes here
38. 43:23Supporting material and software

" related talks

• 22mMySQL Replication: Latest DevelopmentsSujatha Sivakumar · FOSSASIA Summit 2017
• 49mMySQL Replication — Advanced FeaturesPetr Zaytsev · HighLoad++ 2017
• 53mMySQL replication setup, benefits, limitationsRick Golba, Stephane Combaudon · Percona Live MySQL Conference & Expo 2015
• 23mMySQL Group ReplicationVenkatesh Duggirala · FOSSASIA Summit 2017
• 29mEverything You Ever Wanted to Know About MariaDB Replication but Were Afraid to AskEdward Stoever · MariaDB OpenWorks 2023
• 14mThe State of the Art of MySQL ReplicationRicky Setyawan · FOSSASIA Summit 2017
• 43mHow MySQL Replication WorksAndrey Aksenov · HighLoad++ 2014
• 41mAsynchronous Replication Without CensorshipOleg Tsarev · HighLoad++ 2014