….1′,master_user=’rsandbox’,master_password=’rsandbox’,master_port=10001,master_auto_position=1; s0> start slave; # For s1, s3 and s4 mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
… enable GTID replication on slave #1, but not on slave #2: # slave #1 mysql> change master to master_auto_position = 1; mysql> start slave; and let’s create a new table on the master: mysql> create…
Post: How to fix your PRM cluster when upgrading to RHEL/CentOS 6.4
May 29, 2013 By 2 Comments
…) Master/Slave Set: ms_MySQL [p_mysql] (unmanaged) p_mysql:0 (ocf::percona:mysql): Master percona2 (unmanaged) p_mysql:1 (ocf::percona:mysql): Started percona3 (unmanaged) Stopped: [ p_mysql:2...) Master/Slave Set: ms_MySQL [p_mysql] (unmanaged) p_mysql:0 (ocf::percona:mysql): Master percona1 (unmanaged) p_mysql:1 (ocf::percona:mysql): Slave percona2 (unmanaged) p_mysql:2 (ocf::percona:mysql): Slave…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… set up replication filters on the slave, as described in the MySQL manual. You can configure the slave to only replicate a specific…) in between the actual master and the slaves at the bottom of the replication topology. On the top-level master, you leave all filters disabled; on the relay master…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
June 10, 2013 By 8 Comments
It may not be easy to simply switch from regular MySQL replication to using replication using GTIDs 1. Temporary tables – CREATE… slave host is using different storage engine for the respective table on master databases. Also, if BINLOG_FORMAT is not consistent on master/slave…
Comment: ZFS on Linux and MySQL
June 8, 2013 By 17 Comments
…. So OmniOS should only be used as MySQL read slaves behind a pair of Linux based MySQL Masters using Pacemaker. Maybe you guys can…
Post: Multicast replication in Percona XtraDB Cluster (PXC) and Galera
June 5, 2013 By
… isn’t really much different from standard mysql replication. 1 master with 5 async slaves is going to send a separate replication stream… the luxury of not blocking the master from taking writes if bandwidth is constrained and the slaves lag for a bit, not… mysql]# service mysql stop [root@node1 mysql]# service mysql stop [root@node1 mysql]# service mysql start –wsrep_cluster_address=gcomm:// [root@node2 mysql]# service mysql start [root@node3 mysql…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 22, 2013 By 8 Comments
… merge MySQL 5.6 global transaction ID into MariaDB. In MariaDB global transaction ID, it is much easier to switch a slave to GTID. Simply STOP SLAVE on the slave server, CHANGE MASTER to make it use GTID to connect, START SLAVE. There is…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
… design of MySQL 5.6 global transaction ID. In general, there is no ordering implied between events, because multi-threaded slave may put events in a different order on one slave than on another (or on the master). So in… missing. Well, if the user is not using multi-threaded slave, perhaps the notion of “last executed” and “specific point” does…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
Stephane, how are you coping with bug#69095 (replication fails with GTID enabled and master changes from SBR to RBR) and bug#69135 (mysql.slave_master_info is not updated) ?
