… tablespace files while streaming the redo-logs to ensure that all transactions are also captured. The –apply-logs phase simply utilizes the built in crash recovery and applies the redo-logs to…_old Make sure that the files are owned by mysql: chown mysql:mysql /var/lib/mysql/orig_old/* For each table, run: ALTER TABLE…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
…” align=”alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3[/caption] ….11-60.3 release notes. Bugs Fixed: Transaction objects are now allocated calling calloc() directly … page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
Global Transactions Identifiers are one of the new features regarding replication in MySQL 5.6. They open up a lot of opportunities… and restart it: mysql> show slave status\G [...] Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log tells us why the… not on slave #2: # slave #1 mysql> change master to master_auto_position = 1; mysql> start slave; and let’s create a…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
Since my first post on MySQL transaction descriptors optimization introduced in Percona Server 5.5.30-30…. the read-only transactions optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is…_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_file_per_table…
Post: Repair MySQL 5.6 GTID replication by injecting empty transactions
March 26, 2013 By 1 Comment
… using MySQL GTID. Then the question is: Is there any easy way to skip a single transaction? There is! Injecting empty transactions. Let… There are different ways to find the failed transaction. You can examine the binary logs or you can also check Retrieved_Gtid… the START SLAVE the slave checks that transaction 5 is already in its own binary log and that means that it has…
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 … for the transactions first. Under normal async replication, an event will not be written to the slave’s binary unless log_slave… only basic support, primarily because the storage engine is non-transactional and so PXC cannot guarantee the data will remain consistent…
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… #1166888. Package dependency has been changed from abstract mysql to real /usr/bin/mysql file, because rpm packages from Oracle no longer…
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… (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.1.0 'release candidate' for MySQL available for download
May 7, 2013 By Leave a Comment
… for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6 buffer pool dumps can be produced… 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…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… are held for modifications until the transaction commits and that takes an fsync to the redo log by default, so applying Callaghan… can obviously relax that by simply not fsyncing every transaction (innodb_flush_log_at_trx_commit != 1), or work around it with… want this transaction to persist after a crash, it has to get to disk. This has no effect on standard MySQL replication…
