Monday, October 3, 2016

Last Details about the Percona Live Amsterdam Community Dinner 2016

Here are the last details about the Percona Live 2016 Community Dinner hosted at will also do a short talk.  The subject is a surprise !

Friday, September 30, 2016

Percona Live Amsterdam and MariaDB Developer Meeting 2016: Tip to Stay Dry

Or should I say "to avoid getting soaked"...

The Amsterdam weather forecasts for next week is out and even if it looks good for the Percona Live MySQL and (No)SQL Conference (Monday to Wednesday) and for the MariaDB Developer Meeting (Thursday to Saturday), it could still change (or you might suffer the rain in the week-end):

Thursday, September 15, 2016

Please register to the Percona Live Amsterdam Community Dinner 2016

Percona Live Amsterdam is in 3 weeks, and on the evening of the second day of the conference (Tuesday October 4th 2016), there is the traditional Community Dinner.

As last year, is hosting the event and as last year, canal boats will bring attendees from the conference venue to headquarters.

This event involves some planning: Percona needs to arrange for canal boats and needs to order food and drinks and plan for catering staff.  In both cases, too much or not enough is bad for obvious reasons, and this is why we ask you to register.

The normal sales end soon.  After that, commitments need to be made and we will have less flexibility for accommodating more people.

So please help us make the event a success by registering to the Percona Live Community Dinner.

And as a reminder, you can see a picture from last year below, more pictures from the event and boat trip on Percona facebook album.

Saturday, August 20, 2016

A discussion about sync-master-info and other replication parameters

Some time ago, feedback was requested on new replication default after MySQL 5.7.  Some of the suggested default are:
I agree on the suggestions for relay-log-info-repository and relay-log-recovery: they are needed for crash safe replication, and having crash safe replication enabled by default is a good thing.  I have doubts about master-info-repository: I do not see what benefits are introduced by this change.  I have much bigger doubts about sync-master-info and sync-relay-log: those changes bring an illusion of safety, which is bad.  Let's dive in more details about those parameters.

Saturday, July 16, 2016

Understanding Bulk Index Creation in InnoDB (and innodb_sort_buffer_size)

In a previous post, I presented an Unexpected Memory Consumption for Bulk Index Creation in InnoDB.  This was triggered by an increased innodb_sort_buffer_size and as stated in another post: "the sorting algorithm does not scale well with large sort buffers".  In this post, I will present why it does not scale well and I will suggest solutions.

Tuesday, July 5, 2016

Let's meet at Percona Live Amsterdam

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

Monday, April 11, 2016

MySQL Parallel Replication and more talks at Percona Live (April 2016)

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):

Sunday, January 24, 2016

Replication crash safety with MTS in MySQL 5.6 and 5.7: reality or illusion?

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
Update 2018-08-20: it was brought to my attention that MySQL 5.6 with GTID enabled and with sync_binlog != 1 is not replication crash safe, even with single threaded replication.  This is reported in Bug#70659 - Make crash safe slave work with gtid + less durable settings.  Thanks Valeriy for mentioning, in your last blog post, the bug from Sveta Smirnova (Bug#90997) which pointed me to Yoshinori Matsunobu's bug.  To my knowledge, MySQL 5.7 and 8.0 are also affected by this bug, even if this should not be the case.  I will soon open a new bug report about this and will put the bug number below.
    End of updates.

    I will be talking about parallel replication at FOSDEM in Brussel on January 30th and at Percona Live Santa Clara in April (link to the talk descriptions here and here).  Come to one (or both) of those talks to learn more about this subject.