…’d suggest reading over the manual’s description of how replication filtering rules are processed. There are some informative flowcharts in… should state an obvious disclaimer here in that the aforementioned statements reflect only my opinion and not any official Percona position… if you’re not using GTID-based replication. If you are using GTID-based replication, it looks like you’ll need to…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
June 10, 2013 By 8 Comments
… not be easy to simply switch from regular MySQL replication to using replication using GTIDs 1. Temporary tables – CREATE and DROP TEMPORARY… is not supported to perform such type of statements http://mysqlopt.blogspot.co.uk/2013/06/restrictions-on-replication-with-gtids.html
Post: Migrating between MySQL schemas with Percona Xtrabackup
June 10, 2013 By 2 Comments
…, I’ve used Xtrabackup simply to clone a server (for replication or migration) or migrate an existing schema to a new… also included this helpful script to generate all of those statements for steps 7 and 10 in two scripts: mysql -N… name) using –include=”^orig[.]“ (i.e. functional partitioning) Combine with –replicate-rewrite-db Daily backups from production to staging with different…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
…effect on standard MySQL replication from this instance, since MySQL replication is asynchronous. What about semi-sync MySQL replication? It’s actually …… COMMIT multi-statement transactions since it cannot be assumed that those are not applying application logic in between the statements that is…
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
April 17, 2013 By 2 Comments
… makes disconnecting the replica impossible. And again, if you restart replication, it will read events from the first available binary log… supported, which is a great improvement. But the RESET SLAVE statement also behaves differently: mysql> stop slave; Query OK, 0 rows…, you will be able to restart replication, but again as no replication coordinate is specified, replication will start at the beginning of the…
Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available
April 17, 2013 By 2 Comments
… replicated when TOI was used in wsrep_OSU_method variable. This bug was fixed for the case when DROP TEMPORARY TABLE statement was used, but it will still replicate in case DROP TABLE statement is used on a temporary… TABLE AS SELECT statement was running in parallel with the DDL statement on the selected table, in some cases first statement could be…
Post: Is your MySQL buffer pool warm? Make it sweat!
April 16, 2013 By 6 Comments
… for MySQL high availability. Many rely on MySQL’s asynchronous replication to maintain a warm standby server which is flipped into…. The standby server does not process query traffic except for replication. The buffer pool and adaptive hash index on the standby…. This is an important step because update statements that match no rows or insert statements that have duplicate key errors may be…
Comment: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 16, 2013 By 10 Comments
i just did: http://www.percona.com/forums/questions-discussions/percona-xtradb-cluster/10162-xtradb-cluster-only-replicating-ddl-statements innodb tables
Post: Infinite Replication Loop
October 10, 2011 By 2 Comments
… with infinite replication loops. I decided to write a blog post about these infinite loop of binary log statements in MySQL Replication. To…) 2. stop replication on the master having writer role (mysql1) 3. wait until some statements are replicated 4. change the replication master position on… the active master, the loop statements are also replicated from the relay-log but they aren’t not replicated again. Step 3: the…
Post: Can MySQL temporary tables be made safe for statement-based replication?
May 26, 2008 By 8 Comments
… for row-based replication in MySQL 5.1 and later, but most installations I know of are using statement-based replication, even on…. However, since all the statements went into the binlog individually, there’s clearly an opportunity to break replication here. It looks like… MySQL statement-based replication without some risk of breaking slaves. At some point I may test how it works with row-based replication…
