…second post of a series of articles focused on MySQL 5.6 GTIDs. You can find part one here. …# For s0 s0> change master to master_host=’127.0.0.1′,master_user=’rsandbox’,master_password=’rsandbox’,master_… crashed before sending all writes If the binary logs of the master are no longer readable, you …
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
… and two slaves, all running MySQL 5.6 with GTIDs disabled. First …mysql> show slave status\G [...] Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log…mysql> show slave status\G [...] Auto_Position: 1 -> GTID-based positioning # Slave #2 mysql> show slave status\G [...] Auto_Position: 0…
Post: Experiences with the McAfee MySQL Audit Plugin
…test (5.5.28-29.1). This is needed as the plugin needs the offset to some MySQL …#audit_json_socket=1 audit_json_log_file=/var/lib/mysql/audit.log audit_record_cmds=connect,Quit …type”:”activity”,”date”:”1369155747383″,”thread-id”:”6440″,”query-id”:”0“,”user”:”debian-sys-maint”,”priv_user”:”debian-…
Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency
… Schema Benchmark. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using only the…/data basedir=/usr/local/mysql socket=/var/lib/mysql/mysql.sock user=justin innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb… security risks symbolic-links=0 innodb_stats_persistent innodb_stats_auto_update=off [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var…
Post: Migrating between MySQL schemas with Percona Xtrabackup
… the dirty tablespace files while streaming the redo-logs to ensure that all transactions are also captured. … sure that the files are owned by mysql: chown mysql:mysql /var/lib/mysql/orig_old/* For each table, run… on my test VM: Percona Server 5.5.30 Xtrabackup 2.0.6 Some other use cases that come…
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
… supported from MySQL 5.5). If you want to know more details, please read on! MySQL 5.0/5.1 First let’s consider MySQL 5.0 and 5.1. RESET SLAVE will remove the master.info and relay-log.info files as well as all the relay log…
Post: MySQL 5.6 Compatible Percona Toolkit 2.2 Released
… started beta support for MySQL 5.6 in 2.1.8 when 5.6 was still beta. Now that MySQL 5.6 is GA, so… since. Now that we have four base versions of MySQL (5.0, 5.1, 5.5, and 5.6), plus at least four major forks (Percona Server… on its primary objective: analyzing MySQL query logs. So the ability to parse memcached, Postgres, Apache, and other logs was removed. We also…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
…invaluable. Enter MySQL 5.6 with the memcached plugin… As part of the standard MySQL 5.6 GA…’Libmemcached’, $frontendOpts, $memcacheOpts); $timer->start(); for ($i = 0; $i < 100000; $i++) { $cache->save(new Object(), “key_$… using InnoDB under the hood (redo logs, etc). Based on the above numbers, …
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
…Percona XtraDB Cluster (PXC) for MySQL is a hot thing right now and some users jump… not be written to the slave’s binary unless log_slave_updates is enabled, this is similar to Percona… achieve better consistency, if you have an async master <= 5.0 though, you can workaround this by turning off wsrep…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
… in the 2.0 series. New Features: This version of Percona XtraBackup has implemented full support for new MySQL 5.6 features (GTID… #1095972. Percona XtraBackup would fail when preparing the MySQL 5.6 backup if the log files were bigger than 4G on the source server. Bug fixed #1164979. Due to different implementation in MySQL 5.6…

