June 19, 2013

Comment: ZFS on Linux and MySQL

…, but it is just the price you should be willing to pay for ZFS. ZFS LZ4 compression is the best thing… of L2ARC and ZIL. All I am dreaming now is to have LZ4 compressed persistent L2ARC, which is coming soon. 2… pair of Linux based MySQL Masters using Pacemaker. Maybe you guys can get Galera working on OmniOS to solve our lack of…

Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2

… order on one slave than on another (or on the master). So in general “last executed GTID” makes little sense, rather… set of all executed events is needed. And using mysqlbinlog to apply a binlog from a different server from a specific point does not work, you need to apply just the set of events missing. Well, if the…

Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

… from MySQL 5.6 to MariaDB 10.0 or vice versa. You just won’t be able to use the GTID features to automatically pick the correct binlog position when switching to a new master. Old-style replication… compatibility is good. If you have any suggestion of how to make MariaDB compatible without merging all of the crap that…

Post: How to create a new (or repair a broken) GTID based slave with Percona XtraBackup

…- Take a backup from any server on the replication environment, master or slave: # innobackupex /destination/ In the destination folder there will…-a604-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…

Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)

… expected: use CHANGE MASTER TO MASTER_HOST=”: mysql> stop slave; Query OK, 0 rows affected (0.00 sec) mysql> change master to master_host=”; Query OK… CHANGE MASTER TO MASTER_HOST=” trick no longer works: mysql> stop slave; Query OK, 0 rows affected (0,01 sec) mysql> change master to master_host…

Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL

… need to have log_slave_updates enabled on the cluster node acting as async slave for replicated events from the async master to be applied to the other nodes, that is if you have more… an async master, for example like the one described on these two bugs. Galera use writesets to replicate cluster events to the other…

Post: Announcing Percona XtraBackup 2.1.1 GA

… contains new innobackupex –rebuild-threads option that can be used to specify the number of threads started by XtraBackup when rebuilding… changed page tracking feature to perform the Incremental Backups now. Bugs Fixed: innobackupex is using SHOW MASTER STATUS to obtain binlog file and position. This could trigger a bug if the server being backed up was standalone server (neither master

Post: Is your MySQL buffer pool warm? Make it sweat!

… MySQL’s asynchronous replication to maintain a warm standby server which is flipped into service if the active master server has an… that points to the active server of a pair. The passive server has mysqld running and replicating from the active master. In theory, failing over is the simple matter of moving the virtual IP. In practice, it’s slightly more complicated. To

Post: Is Synchronous Replication right for your app?

to semi-sync is: [On a semi-sync replication master] you can’t commit (at all) more than once per RTT.  Applied to… out transaction ordering really, really matters (really!).  By enforcing replication to all nodes, we can (simultaneously) establish global ordering for the… making them (anyone obsessively testing slave position to ensure it’s caught up with the master?). Synchronous replication with PXC and Galera…

Post: Percona Server for MySQL 5.5.30-30.2 now available

… TABLE implementation has been improved. (Laurynas Biveinis) Bugs Fixed: Due to parse error in the percona-server.spec Percona Server rpm…). In the event that a slave was disconnected from the master, under certain conditions, upon reconnect, it would report that it… (Alexey Bychko). Fixed the upstream bug #68197 that caused InnoDB to misclassify internal read operations as synchronous when they were actually…