… replication and GTID replication This time, we will 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 table…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
…’,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; Those of you who have already done these operations with file-based replication…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… the bottom of the replication topology. On the top-level master, you leave all filters disabled; on the relay master you add binary…: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql_install_db under strace, I…
Post: Multicast replication in Percona XtraDB Cluster (PXC) and Galera
June 5, 2013 By
… more the bandwidth required for replication multiplies. Now, this isn’t really much different from standard mysql replication. 1 master with 5 async slaves is going to send a separate replication stream to each, so…
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 …) 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…
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… engine for the respective table on master databases. Also, if BINLOG_FORMAT is not consistent on master/slave db. 3. CREATE TABLE… statements http://mysqlopt.blogspot.co.uk/2013/06/restrictions-on-replication-with-gtids.html
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 27, 2013 By 8 Comments
You can replicate from MySQL 5.6 to MariaDB 10.0 or vice versa. You … the correct binlog position when switching to a new master. Old-style replication will work. That being said, I agree that compatibility… MariaDB compatible without merging all of the crap that is MySQL 5.6 global transaction ID, I would very much like…
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) ?
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
April 17, 2013 By 2 Comments
… replication slave? In short For MySQL 5.0 and 5.1, run STOP SLAVE, CHANGE MASTER TO MASTER_HOST=” and then RESET SLAVE. For MySQL… to MASTER_HOST Fortunately, the documentation also specifies that we can use RESET SLAVE ALL to remove all replication-related configuration: mysql> stop…
Post: Galera Flow Control in Percona XtraDB Cluster for MySQL
May 2, 2013 By 5 Comments
… to Galera is existence of a replication feedback mechanism, unlike anything you find in standard async MySQL replication. It is my belief that… allow replication to resume as soon as possible. An example configuration tuning flow control in a master/slave cluster might be: mysql> set…
