During the design period of a new cluster, it is always advised to have at least 3 nodes (this is the case with PXC but it’s also the same with PRM). But why and what are the risks ? The goal of having more than 2 nodes, in fact an odd number is recommended in [...]
Announcement of Percona XtraDB Cluster 5.5.20 GA release
April 3, 2012 By 11 Comments
I am excited to announce the availability of the GA release of our new product Percona XtraDB Cluster. Percona XtraDB Cluster is a High Availability and Scalability solution for MySQL Users and is based on Percona Server 5.5.20. With this release we make clustering very easy and affordable for everyone. You can convert your existing [...]
Percona Testing: Innodb crash / recovery tests available
December 21, 2011 By Leave a Comment
Not everyone may know this, but there are precious few innodb crash recovery tests available. Some folks have noticed this and asked for something to be done about it, but unfortunately, no tests have been created for the main MySQL branch. The MySQL at Facebook branch has a number of tests that are quite interesting. [...]
Statement based replication with Stored Functions, Triggers and Events
December 16, 2011 By 4 Comments
Statement based replication writes the queries that modify data in the Binary Log to replicate them on the slave or to use it as a PITR recovery. Here we will see what is the behavior of the MySQL when it needs to log “not usual” queries like Events, Functions, Stored Procedures, Local Variables, etc. We’ll [...]
Fishing with dynamite, brought to you by the randgen and dbqp
November 16, 2011 By Leave a Comment
I tend to speak highly of the random query generator as a testing tool and thought I would share a story that shows how it can really shine. At our recent dev team meeting, we spent approximately 30 minutes of hack time to produce test cases for 3 rather hard to duplicate bugs. Of course, [...]
Emulating global transaction ID with pt-heartbeat
November 4, 2011 By 6 Comments
Global transaction IDs are being considered for a future version of MySQL. A global transaction ID lets you determine a server’s replication position reliably, among other benefits. This is great when you need to switch a replica to another master, or any number of other needs. Sometimes you can’t wait for the real thing, but [...]
Infinite Replication Loop
October 10, 2011 By 2 Comments
Last week I helped 2 different customers with infinite replication loops. I decided to write a blog post about these infinite loop of binary log statements in MySQL Replication. To explain what they are, how to identify them… and how to fix them.
Product to try: MySQL/MariaDB-Galera 0.8
June 13, 2011 By 34 Comments
I wrote about Galera about 1.5 years ago: State of the art: Galera – synchronous replication for InnoDB. It was about the 0.7 release, which was more like a proof-of-concept release (though Galera’s developers may not agree with that ) with some serious limitations (like using mysqldump for node propagation). The Galera team heard my [...]
MySQL Limitations Part 2: The Binary Log
October 23, 2010 By 11 Comments
This is the second in a series on what’s seriously limiting MySQL in certain circumstances (links: part 1). In the first part, I wrote about single-threaded replication. Upstream from the replicas is the primary, which enables replication by writing a so-called “binary log” of events that modify data in the server. The binary log is [...]
MySQL Limitations Part 1: Single-Threaded Replication
October 20, 2010 By 16 Comments
I recently mentioned a few of the big “non-starter” limitations Postgres has overcome for specific use cases. I decided to write a series of blog posts on MySQL’s unsolved severe limitations. I mean limitations that really hobble it for major, important needs — not in areas where it isn’t used, but in areas where it [...]
