… are not supported inside transaction. 2. Updates involving non-transactional storage engines – It is not possible to mix non-transactional tables (such as… 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 db. 3. CREATE TABLE…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
June 10, 2013 By 8 Comments
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
Global Transactions Identifiers are one of the new features regarding replication in … be in sync with the master Change configuration for all servers and restart them Use CHANGE MASTER TO to instruct all servers… mysql> change master to master_auto_position = 1; mysql> start slave; and let’s create a new table on the master: mysql> create…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 22, 2013 By 8 Comments
… not to 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… in MariaDB 10.0: https://kb.askmonty.org/en/global-transaction-id/
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
May 30, 2013 By 6 Comments
… bad) part of the design of MySQL 5.6 global transaction ID. In general, there is no ordering implied between events… order on one slave than on another (or on the master). So in general “last executed GTID” makes little sense, rather…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 27, 2013 By 8 Comments
… pick the correct binlog position when switching to a new master. Old-style replication will work. That being said, I agree… all of the crap that is MySQL 5.6 global transaction ID, I would very much like to hear it …
Post: Repair MySQL 5.6 GTID replication by injecting empty transactions
March 26, 2013 By 1 Comment
… there any easy way to skip a single transaction? There is! Injecting empty transactions. Let’s imagine that the replication in slave… a way to ignore that transaction. The way to do it is creating a new empty transaction with it the GTID we… skip some transactions but take in account that by doing this you will end up with data inconsistencies between Master and Slave…
Post: Galera Flow Control in Percona XtraDB Cluster for MySQL
May 2, 2013 By 5 Comments
… trickier than that, because of fc_master_slave (see below). The fc_limit defaults to 16 transactions. This effectively means that this… behind committing transactions from the cluster. gcs.fc_master_slave The fc_limit is modified dynamically if you have fc_master_slave disabled… by the above calculation if fc_master_slave=NO). This yields the number of transactions the recv queue must fall BELOW before…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… on the original node where the transaction is committed) Galera prevents writing conflicts to these pending transactions while they are inflight in… applied to semi-sync is: [On a semi-sync replication master] you can’t commit (at all) more than once per… slave position to ensure it’s caught up with the master?). Synchronous replication with PXC and Galera is no different in…
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
… only basic support, primarily because the storage engine is non-transactional and so PXC cannot guarantee the data will remain consistent…. However, this may work differently when replicating from an async master, for example like the one described on these two bugs… your async master can use ROW based binlog format as well to achieve better consistency, if you have an async master <= 5…
Post: How to create a new (or repair a broken) GTID based slave with Percona XtraBackup
May 9, 2013 By 3 Comments
…- Take a backup from any server on the replication environment, master or slave: # innobackupex /destination/ In the destination folder there will…-080027635ef5:1-4″; slave1 > CHANGE MASTER TO MASTER_HOST=”10.0.1.1″, master_user=”msandbox”, master_password=”msandbox”, MASTER_AUTO_POSITION = 1; 5- Check… see that the slave has retrieved a new transaction with number 5, so transactions from 1 to 5 are already on this…
