… DNS. The post focuses on the key aspects of synchronous replication setup with high-availability guarantees like split-brain immunity. Nobody likes to debug async replication while its broken or do the master-master/master-slave switchover when master is dying/dead… like compression, parallel streaming, encryption, compact backups which can be used for SST (Note, the wsrep_sst_xtrabackup in 5.5…
Post: Percona XtraDB Cluster (PXC) in the real world: Share your use cases!
June 17, 2013 By Leave a Comment
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
… slaves shows that the table has been created everywhere. So once GTIDs are enabled on all servers, you can have some slaves using file-based positioning and some other slaves using GTID-based positioning. This answers the second question: we can have different replication modes…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
… you don’t want to break replication or corrupt your data. Scenario #2: One of the slaves is behind Now let’s… cannot totally forget old-style replication positioning. Conclusion Reconfiguring replication when using GTIDs is usually straightforward: just connect the slave to the correct master…
Post: Multicast replication in Percona XtraDB Cluster (PXC) and Galera
June 5, 2013 By
… Galera uses unicast TCP for replication. Because synchronous replication needs to replicate to all nodes at once, this means 1 copy of your replication message… much different from standard mysql replication. 1 master with 5 async slaves is going to send a separate replication stream to each, so…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
June 10, 2013 By 8 Comments
… may not be easy to simply switch from regular MySQL replication to using replication using GTIDs 1. Temporary tables – CREATE and DROP TEMPORARY tables… the same transaction. The same issue can arise if slave host is using different storage engine for the respective table on master databases. Also, if BINLOG_FORMAT is not consistent on master/slave…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… to set up replication filters on the slave, as described in the MySQL manual. You can configure the slave to only replicate a specific database, a set of databases, or specific tables; you can also configure the slave to replicate everything… if you use the BLACKHOLE storage engine) in between the actual master and the slaves at the bottom of the replication topology. On…
Post: How to fix your PRM cluster when upgrading to RHEL/CentOS 6.4
May 29, 2013 By 2 Comments
If you are using Percona Replication Manager (PRM) with RHEL/CentOS prior to 6.4, upgrading …_vip (ocf::heartbeat:IPaddr2): Started percona1 Master/Slave Set: ms_MySQL [p_mysql] Masters: [ percona2 ] Slaves: [ percona3 percona1 ] [root@percona1 ~]# cat /etc…_vip (ocf::heartbeat:IPaddr2): Started percona3 Master/Slave Set: ms_MySQL [p_mysql] Masters: [ percona2 ] Slaves: [ percona3 ] Stopped: [ p_mysql:2 ] After…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
@Kristian, Well, the (slave) server *knows* whether it is replicating in parallel or not, so it doesn’t have to always manage the general case. When it knows it uses single thread replication the “last executed” assumption is safe.
Post: MySQL Query Patterns, Optimized - Webinar questions followup
June 3, 2013 By 2 Comments
… questions with my complete answers: Q: Can you compare the use of subqueries/multiple joins vs. multiple queries (e.g. temp… better than another equivalent solution. If you’re talking about using a temporary table to store an interim result set, and… other drawbacks to using temporary tables in this way, for example when using replication, a temporary table could vanish if the slave restarts and…
Post: Percona Server for MySQL 5.5.31-30.3 now available
May 24, 2013 By Leave a Comment
… that could cause a memory leak if query cache was used together with InnoDB. Bug fixed #1170103. Fixed the RPM packaging… a slave was running with its binary log enabled and then restarted with the binary log disabled, Crash-Resistant Replication could overwrite…
