June 19, 2013

Comment: Finding your MySQL High-Availability solution – The questions

…types of failures: * mysql becomes unavailable (best case) * mysql connection are unresponsive connection happen very slowly * mysql connection are unresponsive … master when the worst happens. The main dis-advantage is the replication delays with muti-master. This is where muti-threaded slaves

Post: Implementing efficient counters with MySQL

replication, especially as it has to serialize transactions on the slave which could be executed in parallel on the masterMySQL server. If you rather use existing solutions you can use memcache + another mysql instance (or simply the database which is not replicated… doing these delayed updates you …

Post: Figuring out what limits MySQL Replication

… cloning the master using LVM Snapshot and found it was taking quite a while to catch up, which highlighted replication could be the limiting factor for this system quite soon, so I decided to check what is limiting MySQL Replication speed… restarting slave does not pick up the change. I of course could just restart MySQL but this would make replication to be delayed few…

Comment: Thoughts on MySQL Replication

delays and backlogs and it can also prevent a slave from catching up in a timely fashion. The MySQL team needs to redesign replication… technique effectively replicates the simultaneous query nature of the master‘s original queries and allows for much more timely replication on the slave. This…

Comment: Implementing Parallel Replication in MySQL

… limitation of the MySQL binary log is that it serialises transactions on the master side. This… transaction in one database / SQL thread will delay replication of short transactions in another remains valid … seems to me that as such delays occur on the slave, more binlog stream will become…

Comment: No more MySQL Crash Safe Replication in 5.0 ?

… InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 1604, file name mysql-bin.000001 InnoDB: Last MySQL binlog file …name ./mysql-bin.000001 The difference is consistently 27, which corresponds to unimportant binlog events: /*!40019 SET @@session.max_insert_delayed_…

Comment: Using MyISAM in production

… using delay_key_write on slave servers is good one. You want to do insert/update only on master anyway as otherwise it will not be replicated… is actually partialy solved by using MMAP in MySQL 5.1 but you still can’t configure …

Post: Using MyISAM in production

…. Lock priorities. By default MySQL treats updates as higher …for causing unexpected slowdowns. delay_key_writes Whatever way you …slave servers. If it crashes you can simply re-clone it. Make sure however to have at least one proper master to fall back to. Also be worried about replication