… log coordinates and GTID information. That information is also printed by innobackupex after backup is taken: innobackupex: MySQL binlog position: filename ‘mysql-bin.000002′, position 1232, gtid_executed c777888a-b6df-11e2-a604-080027635ef5:1-4 2- Apply the logs to… see that the slave has retrieved a new transaction with number 5, so transactions from 1 to 5 are already on this…
Post: How to create a new (or repair a broken) GTID based slave with Percona XtraBackup
May 9, 2013 By 3 Comments
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… (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
… ’0′, PRIMARY KEY (`hid`,`mid`,`id`) ) and transactions are: $HID=rand(0,10000) // distributed by uniform… = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block_size=4096 …_repair_threads = 1 myisam_recover socket=/var/lib/mysql/mysql.sock user=root skip-grant-tables TokuDB-…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… exact same pattern when looking at transaction latency; the baseline numbers are roughly…=0 –percentile=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: How InnoDB handles REDO logging
February 3, 2011 By 19 Comments
…that affects both response time and throughput – The transaction log. The InnoDB transaction log handles REDO logging, this is the mechanism that provides the A… log at all, your transaction will never complete. Both the MySQL configuration and hardware will affect the speed at which InnoDB can log…
Post: How to create/restore a slave using GTID replication in MySQL 5.6
February 8, 2013 By 7 Comments
…. 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…
Post: Percona XtraDB Cluster (PXC): what about GRA_*.log files ?
December 19, 2012 By Leave a Comment
… apply one transaction. For each of those file, a corresponding warning or error message is present in the mysql error log file. Those… log file: [root@node2 mysql]# ls GRA_*.log GRA_3_3.log [root@node2 mysql]# file GRA_3_3.log GRA_3_3.log: data [root@node2 mysql..._3.log GRA_3_3.log: data [root@node2 mysql]# file GRA_3_3-bin.log GRA_3_3-bin.log: MySQL replication log [root@node2 mysql]# mysqlbinlog…
Post: How to Monitor MySQL with Percona's Nagios Plugins
February 22, 2012 By 11 Comments
… installations) or a system administration mistake to delete one of MySQL‘s log or data files from disk. The database server will… checks whether MySQL owns every file and directory within its data directory. InnoDB is getting stuck, has long-running transactions, or other problems. The pmp-check-mysql-innodb plugin checks for several indicators of…
Post: Should MySQL update the default innodb_log_file_size?
November 21, 2011 By 37 Comments
… storage engine in MySQL, is it time to update the default configuration for the InnoDB log file size (innodb_log_file_size) setting… installation. MySQL 5.5 increased the default buffer pool size to something more sane (128MB instead of 8MB), but the log file… simply can’t run a “real” server with 10MB of transaction logs. What’s a sane value? I’d say that something…
Post: Implications of Metadata Locking Changes in MySQL 5.5
February 1, 2013 By 9 Comments
… for the transaction to commit. For the reasons described above the implementation of Metadata Locking was changed, starting MySQL 5… | 0.000005 | | sending cached result to clien | 0.000011 | | logging slow query | 0.000002 | | cleaning up | 0.000002 | +——————————–+———-+ 8…
