When mysql shows Slave_IO_Running and Slave_SQL_Running is false, then there is much evidence that the current slave relay log is broken. show slave status \G then looks for example like this: mysql> show slave status \G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: master.example.com Master_User: […]
I´ve already pointed out here, that you can easily restart a replication. But you have to know that the replication isn´t working. Instead of continuously typing “CHECK SLAVE STATUS\G” in mysql i´ve decided to use nagios for that. If something is wrong, i get a mail and a notification in […]
If the mysql-replication is broken, there are two ways to fix the problem: skip the error rebuild the replication In some cases you could easily skip error. If you for example execute the same INSERT on both server. Skip the error Login into mysql as root: STOP SLAVE; SET GLOBAL […]
In contrast to a master-slave replication in a master-master replication changes made on one server are immediately available on both. The setup of a master-master-replication is similar to a master-slave-replication. I show here only the differences (for the basics see mysql master-slave-replication). In the following to old master remains as […]
In a master-slave replication on the slave are the databases of the master 1:1 available. Changes performerd on the master are immediately available on the slave (as long as you don´t user master_delay). Thus, it is not a true backup solution. Master setup: Change the section [mysqld] in /etc/my.cnf. Make […]