May 25, 2012

Comment: Emulating global transaction ID with pt-heartbeat

… i hear the talk about failover from intermediate slaves to master and knowing that mysql does not have a way match the transactions… C to start replicating from A with “relay_master_log_file: test_file , exec_master_log_pos: 2399″ and ignore the duplicate key errors for some time untill replication catches up…

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

to the cluster. The “replication_info” config setting is only changed when a new master is elected. So how toto edit it, so use the command that the mysql RA uses, which is: crm_attribute –type crm_config –name replication_info -s mysql_replication

Post: How Does Semisynchronous MySQL Replication Work?

… also committed successfully. In MySQL‘s semi-synchronous replication, the commit completes before the transaction is even sent to any of the replicas… on the master. However, that is not what happens in semi-synchronous replication. And if there is an error in semi-synchronous replication, such…

Post: How to Monitor MySQL with Percona's Nagios Plugins

mysql-replication-running checks that replication is functioning correctly. Replicas have different data than their master. In addition to delay or failure, replication

Post: Master-Master or Master with Many Slaves

…having application error which deletes/trashes all the data and gets replicated to all the slaves ? When you compare master-master to multiple …master-N-slave configuration will be saturated much faster because it has to handle much more write load. Especially keeping into account MySQL replication

Post: Troubleshooting Relay Log Corruption in MySQL

…, or a bug in the master‘s or slave’s MySQL code. If you want to check the master‘s binary log or slave… the master are OK you can just run SHOW SLAVE STATUS on slave experiencing error and use CHANGE MASTER TO to re-point replication to Relay_Master_Log_File:Exec_Master_Log_Pos: localhost:(none)> slave…

Post: Percona XtraDB Cluster Feature 2: Multi-Master replication

…-sync situation, as it regularly happens with regular MySQL replication if you imprudently write to the wrong server. This is long-waited feature…. This gap between slave and master is the reason why this replication named “virtually synchronous replication“, not real “synchronous replication” The described behavior of… errors code after “COMMIT” query, but I saw many applications that do not do that. So, if you plan to use Multi-Master

Post: The story of one MySQL Upgrade

… but first we decide to see how broad is it. We let Slave to replicate with skip-slave-errors=1105 to see if we get… we need to go back to MySQL 5.0 on the master. To do this we set up replication from Percona Server 5.1 back to MySQL 5.0 and performed the same checks again – happily replication

Post: Statement based replication with Stored Functions, Triggers and Events

error_code=0 SET TIMESTAMP=1323820314/*!*/; INSERT INTO t VALUES(YEAR(CURDATE())) If later we need to promote a Slave to Master we will need to do some steps to enable all the events replicated from the master

Post: Can MySQL temporary tables be made safe for statement-based replication?

A while ago I wrote about how to make MySQL replication reliable, part of which is to eliminate temporary tables. The idea is this…’s the error I thought I’d see. Even though it was used entirely within one transaction on the master, the temporary… the master — is what’s important. In summary, I still don’t see any way to use temporary tables with MySQL statement-based replication