Working with customer, I faced pretty nasty bug, which is actually not rare situation , but in this particular there are some lessons I would like to share. The case is pretty much described in bug 55981, or in pastebin. Everything below is related to InnoDB-plugin/XtraDB, but not to regular InnoDB ( i.e in MySQL [...]
Replication of MEMORY (HEAP) Tables
Some Applications need to store some transient data which is frequently regenerated and MEMORY table look like a very good match for this sort of tasks. Unfortunately this will bite when you will be looking to add Replication to your environment as MEMORY tables do not play well with replication.
Percona Launches New Support Option for MySQL
We’ve just announced a new support offering for MySQL. There’s a press release here, and product information page here. But what does this new service really mean for you, in practical terms? This is actually important — it will open up a range of new choices for you. I’ll explain two major points that matter [...]
Scaling: Consider both Size and Load
So lets imagine you have the server handling 100.000 user accounts. You can see the CPU,IO and Network usage is below 10% of capacity – does it mean you can count on server being able to handle 1.000.000 of accounts ? Not really, and there are few reasons why, I’ll name most important of them: [...]
When should you store serialized objects in the database?
A while back Friendfeed posted a blog post explaining how they changed from storing data in MySQL columns to serializing data and just storing it inside TEXT/BLOB columns. It seems that since then, the technique has gotten more popular with Ruby gems now around to do this for you automatically.
Upgrading MySQL
Upgrading MySQL Server is a very interesting task as you can approach it with so much different “depth”. For some this is 15 minutes job for others it is many month projects. Why is that ? Performing MySQL upgrade two things should normally worry you. It is Regressions – functionality regressions when what you’ve been [...]
Faster MySQL failover with SELECT mirroring
One of my favorite MySQL configurations for high availability is master-master replication, which is just like normal master-slave replication except that you can fail over in both directions. Aside from MySQL Cluster, which is more special-purpose, this is probably the best general-purpose way to get fast failover and a bunch of other benefits (non-blocking ALTER [...]
High-Performance Click Analysis with MySQL
We have a lot of customers who do click analysis, site analytics, search engine marketing, online advertising, user behavior analysis, and many similar types of work. The first thing these have in common is that they’re generally some kind of loggable event. The next characteristic of a lot of these systems (real or planned) is [...]
How would you compress your MySQL Backup
Backing up MySQL Database most people compress them – which can make a good sense in terms of backup and recovery speed as well as space needed or be a serious bottleneck depending on circumstances and approach used. First I should mention this question mainly arises for medium and large size databases – for databases [...]
Confusing MySQL Replication Error Message
I already wrote about some MySQL Error Messages which are confusing, here is one more:
1 2 3 4 5 6 7 8 9 10 | 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444286437 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444292333 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444292333 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444294573 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444294573 080603 20:53:10 [Note] Slave: received end packet from server, apparent master shutdown: 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'master-bin.003676' position 444298239 080603 20:53:10 [Note] Slave: connected to master 'repl@host.com:3306',replication resumed in log 'master-bin.003676' at position 444298239 |
After setting up new slave Server I’m getting error log file flooded with messages like this and there is no hint in the message what would explain what is wrong. In fact the issue in this case is (because [...]

