May 24, 2012

Post: Reasons for MySQL Replication Lag

a single thread and something which might not look like a lot of load for your powerful master may be enough toin other case 10-20% difference in data size can be the difference between slave never lags and slave never is able to catch up. MySQL

Post: Recovery beyond data restore

to get a standby MySQL server or at least synchronously replicated master binary logs. If you can‘t loose any single transaction you’ve canto the slave. What if you can ? The switch to the slave in this case is not very easy too – all slaves can be on different positions at the master

Post: KISS KISS KISS

single master and should have done sharding functional partitioning or something else. Complex Replication There are impressive numbers out there on how many slavesbe able to handle all traffic from capacity planning standpoint anyway. At the same time slave can be perfect to be

Post: Upgrading MySQL

in MySQL 4.1 or changing JOIN evaluation in 5.0 (which could both cause different result set or make query not runnable in MySQLMaster. In many cases you can leave the ex-Master as a slave so you can fail back to the old version easily if you need to. In

Post: Implementing efficient counters with MySQL

a counter how many time given object – blog post, forum thread, image, movie etc was viewed. This is sometimes handy feature but it can beto serialize transactions on the slave which could be executed in parallel on the master. So we learned it can be quite nasty, so how can

Post: High-Performance Click Analysis with MySQL

in MySQL 5.0 and earlier, doing the work on a slave, then piping the results back up to the mastera lot of joins between fact and dimension tables, and so on.  With careful tweaking, many of these things can be overcome, but how

Post: Managing Slave Lag with MySQL Replication

slaves used for long reporting queries can have queries running for hours which stalls replication progress for this time. As MySQL Replication goes in singleMaster-Master setup do not forget to disable binary logging with SET SQL_BIN_LOG=0 before you run ALTER TABLE query. Replication Overload Many

Post: Debugging problems with row based replication

in DML statements. A statement based replication slave can get out of sync with the master fairly easily, especially if data is changed on the slaveMySQL slaves to prevent accidental changes in data from happening! *edit* The MySQL 5.1 default binary logging format changed back to STATEMENT in MySQL

Post: The story of one MySQL Upgrade

in MySQL 5.0. There are number of ways the problem can be solved but first we decide to see how broad is it. We let Slave toto be fixed. At this point we were confident enough Slaves can handle the traffic and we could put them in production. Before upgrading Master

Comment: Master-Master or Master with Many Slaves

a single master and two slaves that can be promoted to master. We can just create as many shards as we need writes.” Well that if fine when. To often however people use too many slaves using replication Instead of partitioning. By the way, how many shards do you have and how many