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 [...]
How Percona does a MySQL Performance Audit
Our customers or prospective customers often ask us how we do a performance audit (it’s our most popular service). I thought I should write a blog post that will both answer their question, so I can just reply “read all about it at this URL” and share our methodology with readers a little bit. This [...]
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 [...]

