FOSDEM is next weekend and I am talking about Parallel Replication on Friday, February 2nd at the MySQL Pre-FOSDEM Day (there might be tickets left in case of cancellation, attendance is free of charge). During this talk, I will show benchmark results of MySQL 8.0 parallel replication on Booking.com real production environments. I thought I could share a few things before the talk so here it is.
Saturday, January 27, 2018
Thursday, January 11, 2018
This is the third post in the series on Write Set in MySQL. In the first post, we explore how Write Set allows to get better parallel replication in MySQL 8.0. In the second post, we saw how the MySQL 8.0 improvement is an extension of the work done in MySQL 5.7 to avoid replication delay/lag in Group Replication. In this post, we will see how Write Set is used in Group Replication to detect conflicts in multi-writer mode during certification. We will also see the impacts, on conflict detection, of the Write Set bug that I presented in the first post.
Monday, January 8, 2018
In my previous post, I write that Write Set is not only in MySQL 8.0 but also in MySQL 5.7 though a little hidden. In this post, I describe Write Set in 5.7 and this will bring us in the inner-working of Group Replication. I am also using this opportunity to explain and show why members of a group can replicate faster than a standard slave. We will also see the impacts, on Group Replication, of the Write Set bug that I presented in my last post.
Wednesday, January 3, 2018
In my MySQL Parallel Replication session at Percona Live Santa Clara 2017, I talked about a bug in Write Set tracking for parallel replication (Bug#86078). At the time, I did not fully understand what was going wrong but since then, we (Engineers at Oracle and me) understood what happened and the bug is supposed to be fixed in MySQL 8.0.4. This journey thought me interesting MySQL behavior and bug reporting practices. In this post, I am sharing both in addition to some insight on Write Set tracking for parallel replication.