May 26, 2012

Post: Reasons for MySQL Replication Lag

slave read traffic from non warmed up slave will often cause warmup to be longer, because it has to happen in the single thread. Inreplication lag. Same may happen with operating system and other system software involved. In could be even system which queries mysql

Post: Upgrading MySQL

in MySQL history when issues would only happen at high load. You can do this inSlave(s) If you want to minimize downtime it is best to use MySQL Replication for upgrade. Once you have setup slave

Post: MySQL Replication vs DRBD Battles

to the point what we’re comparing here – it is mainly DRBD to MySQL Replication based techniques (lets leave MySQLto have lost transactions which may happen with async replication. Another similar case is when you’re looking to ensured consistency – MySQL Replication

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

to a level where we started looking at other ways of achieving higher availability using MySQL replicationto MMM If the master fails, a new master is promoted from the slaves, no master toto the main Pacemaker resource agents branch. More testing and cleaning will be needed before that happen

Post: MongoDB Approach to database synchronization

MySQL Replication when your master goes down it is possible for some writes to be executed on the master, but not on the slaveWhat is really interesting – it should be possible to apply the same concept to MySQL Replicationto Slave happened and they can be dumped to local file (in case one wants to

Post: MySQL Master-Master replication manager released

MySQL Master-Master replication (often in active-passive mode) is popular pattern used by many companies using MySQL…. If Active server fails in the pair both …to prevent application mistakes. What will happen if you will write to the slave because of application error ? Well you’ll break replication

Post: Faster MySQL failover with SELECT mirroring

replication, which is just like normal master-slave replication except that you can fail over in both directions. Aside from MySQLwhat‘s happening that I’m still investigating and may write more about later, in this particular case. So what

Post: Using MyISAM in production

to disk, but it also comes at great danger if MySQL Server crashes or power goes down. In case crash happensfailing to run, wrong result sets or crashes. Here is my list what I think MyISAM tables are good toto have at least one proper master to fall back to. Also be worried about replication

Post: State of the art: Galera - synchronous replication for InnoDB

MySQL Replication Clusters”. It was impressed as I personally always wanted it for InnoDB, but we had it inhappens with whole cluster. – Heterogeneous-database replication. It is not here yet, and I do not know what‘s in

Post: KISS KISS KISS

slaves people run and how complex replication topologies with multiple tiers filtering and writes to some intermediary slavesto fail. Unless you’re Google scale with failures happeningMySQL industry practices (which we also covered in a great depth in