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,
6 Older Entries »
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
Yes, another post about my talks at Percona Live Santa Clara: I obviously still have things to share. This time, I will focus on my parallel replication talks by giving a short preview.
I have two parallel replication talks at Percona Live:
MySQL/MariaDB Parallel Replication: inventory, use cases and limitations (Wednesday talk) MySQL Parallel Replication: all the 5.7 (and some of the 8.0)
In a previous post, I listed all the Booking.com talks at Percona Live. In this post, I will give more details about my talks.
As a reminder, the list of my talks is the following:
Monitoring Booking.com without looking at MySQL (Thursday keynote) The two little bugs that almost brought down Booking.com (Tuesday Lightning Talk) MySQL/MariaDB Parallel Replication: inventory, use cases and
In a week, me and some Booking.com colleagues will be in Santa Clara for Percona Live.
Booking.com is sponsoring the conference and we will be present at the Monday Evening Reception. You do not need a tutorial pass to attend the dinner (even if it is on the tutorial day): any valid pass will do. If you do not have your ticket yet, it is time to register (you can use the discount code “
MySQL 5.7 introduced the LOGICAL_CLOCK type of multi-threaded slave (MTS). When using this type of parallel replication (and when slave_parallel_workers is greater than zero), slaves use information from the binary logs (written by the master) to run transactions in parallel. However, enabling parallel replication on slaves might not be enough to get a higher replication throughput (VividCortex
I have a new blog post on blog.booking.com describing MariaDB 10.1 Optimistic Parallel Replication (with benchmark results):
Evaluating MySQL Parallel Replication Part 4: More Benchmarks in Productionhttp://blog.booking.com/evaluating_mysql_parallel_replication_4-more_benchmarks_in_production.html
If you want to know more about MySQL/MariaDB Parallel Replication and if you are attending
I am very happy that my talk, MySQL Parallel Replication: inventory, use-cases and limitations, is included in the Sneak Peek of Percona Live Amsterdam. As a member of the Conference Committee, I knew this was being discussed, but I refrained from commenting on discussion about my talk and the submissions of my colleagues from Booking.com.
Mentioning the conference committee, as you can guess,
In a few days, I will be flying to San Francisco and then making my way to Santa Clara to attend the Percona Live Conference. On the last day of the conference (Thursday), I will speak about MySQL Parallel Replication. I hope to see you there and I will he happy to answer questions you might have (on this subject and others):
Thursday at 12:50 pm: MySQL Parallel Replication: inventory,
Reminder: MTS = Multi-Threaded Slave.
Update 2017-04-17: since the publication of this post, many things happened:
the procedure for fixing a crashed slave has been automated (Bug#77496) Bug#80103 as been closed at the same time as Bug#77496 but I still think there are unfixed things, see Bug#81840
End of update 2017-04-17.
I will be talking about parallel replication at FOSDEM in Brussel on
6 Older Entries »