June 20, 2013

Post: Choosing a MySQL HA Solution - Post-Webinar Q&A

… 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… messing around with this again at some point in the future, but I’m not optimistic that this is a viable use case…

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

…on all servers, but not something in the middle. What if we try to reconfigure the master? This time, replication on slave #1 will stop: …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

mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave; # And then check the number of records from the t tablereplication positioning. Conclusion Reconfiguring replication when using GTIDs is usually straightforward: just connect the slave to the

Post: MySQL Query Patterns, Optimized - Webinar questions followup

tables in this way, for example when using replication, a temporary table could vanish if the slave restarts and then subsequent queries against the temp tablein this case to force MySQL to scan the `title` table first, grouping by kind_id in index order.  This made the first table in the

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

MySQL is a hot thing right now and some users jump right inreplication, an event will not be written to the slave‘s binary unless log_slave_updates is enabled, this is similar to Percona XtraDB Cluster in

Post: Is Synchronous Replication right for your app?

MySQL replication from this instance, since MySQL replication is asynchronous. What about semi-sync MySQL replication? It’s actually much worse than Galera.  As I illustrated inthe first is still in the local apply queue on their nodes will get a deadlock error. So, the best case (which may not

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

in the wsrep_node_incoming_address. Bug fixed #1082406 (Alex Yurchenko). Dropping a non-existing temporary table would be replicated when TOI was used inreplication conflict and leave a slave hanging. Bug fixed #1130888 (Seppo Jaakola). If MySQL replication

Post: Repair MySQL 5.6 GTID replication by injecting empty transactions

MySQL 5.6 GTID replication using two different methods. I didn’t mention the famous SET GLOBAL SQL_SLAVEthe replication in slave server is notthe SHOW SLAVE OUTPUT as we can see in the example. This slaveSlave servers. pt-table-checksum can help you here, which is found in Percona Toolkit for MySQL

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

replication feedback mechanism, unlike anything you find in standard async MySQL replication. It is my belief that theslave disabled (which it is by default). This mode actually adjusts the fc_limit dynamically based on the number of nodes in the cluster. The

Post: Announcing Percona XtraBackup 2.1.1 GA

the backups. innobackupex now uses Perl’s DBD::MySQL package for server communication instead of spawning the MySQLthe server being backed up was standalone server (neither master nor slave in replication) and binlog information wasn’t available. Fixed by not… assume the table has been dropped if the