October 22, 2014

max_allowed_packet and binary log corruption in MySQL

The combination of max_allowed_packet variable and replication in MySQL is a common source of headaches. In a nutshell, max_allowed_packet is the maximum size of a MySQL network protocol packet that the server can create or read. It has a default value of 1MB (<= 5.6.5) or 4MB (>= 5.6.6) and a maximum size of 1GB. […]

Troubleshooting Relay Log Corruption in MySQL

Have you ever seen the replication stopped with message like this: Last_Error: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the […]

MySQL Replication: ‘Got fatal error 1236′ causes and cures

MySQL replication is a core process for maintaining multiple copies of data – and replication is a very important aspect in database administration. In order to synchronize data between master and slaves you need to make sure that data transfers smoothly, and to do so you need to act promptly regarding replication errors to continue […]

Errant transactions: Major hurdle for GTID-based failover in MySQL 5.6

I have previously written about the new replication protocol that comes with GTIDs in MySQL 5.6. Because of this new replication protocol, you can inadvertently create errant transactions that may turn any failover to a nightmare. Let’s see the problems and the potential solutions. In short Errant transactions may cause all kinds of data corruption/replication […]

8 common (but deadly) MySQL operations mistakes and how to avoid them

January 22 I gave a presentation on “How to Avoid Common (but Deadly) MySQL Operations Mistakes” for Percona MySQL Webinars. If you missed it, you can still register to view the recording and my slides. Thanks to everyone who attended, and especially to folks who asked the great questions. I answered as many as we […]

High-availability options for MySQL, October 2013 update

The technologies allowing to build highly-available (HA) MySQL solutions are in constant evolution and they cover very different needs and use cases. In order to help people choose the best HA solution for their needs, we decided, Jay Janssen and I, to publish, on a regular basis (hopefully, this is the first), an update on […]

Percona Server 5.6.13-60.5 third Release Candidate is now available

Percona is glad to announce the third Release Candidate of Percona Server 5.6.13-60.5 (downloads are available here and from the Percona Software Repositories). The final release is almost ready. Thank you to everyone who has been testing and filing bugs. You’ve been a big help and we can’t wait for you to see the fantastic […]

Percona Server 5.1.71-14.9 is now available!

Percona is glad to announce the release of Percona Server 5.1.71-14.9 on August 27th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.71, including all the bug fixes in it, Percona Server 5.1.71-14.9 is now the current stable release in the 5.1 series. All of Percona‘s software is open-source and free, all the details of the release […]

Percona Server 5.5.33-31.1 is now available

Percona is glad to announce the release of Percona Server 5.5.33-31.1 on August 27th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.33, including all the bug fixes in it, Percona Server 5.5.33-31.1 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release […]

Migrating between MySQL schemas with Percona Xtrabackup

Recently, I was working with a client that asked about using Percona Xtrabackup to take a snapshot of a particular MySQL schema and then reload it with a different schema name on the same server.  It caught me off guard because I’d never really thought about it – typically, I’ve used Xtrabackup simply to clone […]