May 25, 2012

Post: Managing Slave Lag with MySQL Replication

how far MySQL may fall behind and how to keep replication from lagging. The lag you will see will vary a lot from application to the application andmaster you should expect Slave lag spike for at least this amount of time (assuming it takes the same time Master and Slave to

Post: Percona Replication Manager, a solution for MySQL high availability with replication using Pacemaker

and writer, will be located on the master During a master switch, connections are killed on the demoted master to avoid replication conflicts All slavesMaster and Slave. Intervals must not be the same. Following the mysql primitive declaration, the primitives for 3 reader vips and

Post: Reasons for MySQL Replication Lag

and slave never is able to catch up. MySQL or OS version changesMySQL version changes (even minor upgrade) may introduce issues which causes replication

Post: MySQL Replication vs DRBD Battles

MySQL Master-Master replication I can add and index on passive node, wait it to catch up and switchto ensured consistency – MySQL Replication can out of sync – and there is bunch of tips in documentation of how to

Post: Using MMM to ALTER huge tables

switch masters Once standby servers (only db2 in our case) have caught-up, we are ready tomaster) and db1 is back on-line for a failover. There are two ways to do it: 6. Allow replication to

Post: How SHOW SLAVE STATUS relates to CHANGE MASTER TO

…you probably know MySQL Replication (statement based) works by fetching statements from MASTERs binary log and executing them on the SLAVE. Since MySQL 4.0 this…SQL thread and IO threads close enough to share same master log file. Only in rare cases of switching master binary log file or replication

Post: MySQL Master-Master replication manager released

master-master and bunch of slaves. Typically you would define “roles” for example READER and WRITER roles for most simply case and assign them toswitch happens “dirty” way potentially risking replication inconsistencies. This is very handy if you want to restart one of servers in clusters to

Post: Faster MySQL failover with SELECT mirroring

MySQL configurations for high availability is master-master replication, which is just like normal master-slave replicationto watch the traffic on the active master and replay SELECT queries against the passive one. I timed the results and

Post: MySQL Northern European Customer Conference

switch from MyISAM to Falcon. It was rather interesting to hear a lot about features of new storage engines such as Nitro andMySQL Enterprise from MySQL Marketing Materials . There is not much of technical insight otherwise – pretty simple site, master slave replication, plans to

Post: Recovery beyond data restore

switch to the slave in this case is not very easy too – all slaves can be on different positions at the master and you need tomaster (and they will be replicated down to all slaves) the faster however (especially if you have many tiers of replication) is to bring all slaves to