…Transactions Identifiers are one of the new features regarding replication in MySQL 5.6. …mysql> show slave status\G [...] Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log … # Slave #2 mysql> show slave status\G [...] Auto_Position: 0 -> File-based positioning Conclusion Enabling GTID-…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
…alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3….3 release notes. Bugs Fixed: Transaction objects are now allocated calling calloc… if changed page tracking is enabled. Bug fixed #1184517. Missing path … used to hold the log system mutex for the log reads needlessly, potentially …
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
Galera/Percona XtraDB Cluster (PXC) for MySQL is a hot thing right now and some users jump … to go through these basics. log_slave_updates is REQUIRED You need to have log_slave_updates enabled on the cluster node acting… transactions first. Under normal async replication, an event will not be written to the slave’s binary unless log_slave_updates is enabled…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… instead of failing or returning immediately if there is a transaction that executed a query which opened that table. Bug fixed… Percona Server for MySQL 5.5.28-29.3 which could cause a server to hang when binary log is enabled. Bug fixed… (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
May 6, 2013 By 1 Comment
… that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread. Percona XtraBackup…_info when doing the backup of MySQL and Percona Server 5.6 with the GTID mode enabled. Example of how this information…. Percona XtraBackup would fail when preparing the MySQL 5.6 backup if the log files were bigger than 4G on the source…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
May 7, 2013 By Leave a Comment
… that are caused by the log records in the transactional log being overwritten before they are copied by the log copying thread. Percona XtraBackup now stores the GTID value in the xtrabackup_binlog_info when doing the backup of MySQL and Percona Server 5.6 with the GTID mode enabled. Example of how this information…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… instead of failing or returning immediately if there is a transaction that executed a query which opened that table. Bug fixed… Percona Server for MySQL 5.5.28-29.3 which could cause a server to hang when binary log is enabled. Bug fixed… (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… pattern when looking at transaction latency; the baseline … time-based flushing enabled actually produces better …=95 \ –mysql-user=root –mysql-socket=/tmp/mysql.sock –mysql-table-engine=innodb…log_buffer_size = 128M innodb_flush_log_at_trx_commit = 1 innodb_log_file_size = 1G innodb_log…
Post: Auditing login attempts in MySQL
December 28, 2012 By 4 Comments
…logs. General Query Log The first option is the General Query Log. Let’s see an example: Enable the log: general_log_file = /var/log/mysql/mysql.log general_log… 14 UPDATE_COMMANDS: 103 OTHER_COMMANDS: 3556 COMMIT_TRANSACTIONS: 0 ROLLBACK_TRANSACTIONS: 0 DENIED_CONNECTIONS: 2 LOST_CONNECTIONS: 16 …
Post: How to create/restore a slave using GTID replication in MySQL 5.6
February 8, 2013 By 7 Comments
… is that if you want GTID support log_slave_updates will need to be enabled in slave server and the performance impact…. MySQL keeps two global variables with GTID numbers on it: gtid_executed: it contains a representation of the set of all transaction logged in the binary log gtid_purged: it contains a representation of the set of all transactions deleted from the binary log So…
