… (and in my opinion bad) part of the design of MySQL 5.6 global transaction ID. In general, there is no ordering implied… in a different order on one slave than on another (or on the master). So in general “last executed GTID” makes…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
Post: Repair MySQL 5.6 GTID replication by injecting empty transactions
… find the failed transaction. You can examine the binary logs or you can also check Retrieved_Gtid_Set and Executed_Gtid… includes an overview of MySQL 5.6 GTID that can help people to start working with this new feature in MySQL 5.6. Here are the slides from that session. I hope you find it useful: MySQL 5.6 GTID in a…
Post: Percona Server for MySQL 5.5.30-30.2 now available
…MySQL version 5.5.30-30.2[/caption] Percona is glad to announce the release of Percona Server for MySQL 5.5… to assertion errors in the log parser or bad changed page data. Bug fixed #1108613 (…#1163439 (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_…
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
… short For MySQL 5.0 and 5.1, run STOP SLAVE, CHANGE MASTER TO MASTER_HOST=” and then RESET SLAVE. For MySQL 5.5 and 5.6, run… 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… default values. This means that if you run START SLAVE (or if it’s done automatically, for instance when restarting the…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
…_SELECT test for glibc and jemalloc allocators. Observations: = MySQL 5.5.30 – throughput of MySQL 5.5.30 with glibc is limited first of all by… – jemalloc helps MySQL 5.5.30 to fix issues with malloc scalability but still scanning of the transaction list causes performance drop = MySQL 5.6.10… almost no difference in results between runs either with glibc or jemalloc
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
… a major problem for MySQL scalability? The scan is performed under kernel_mutex (or trx_sys->mutex in 5.6) and that is one… scan in MySQL 5.5 basically kills throughput on high concurrency. The picture changes dramatically when the read-only optimization in MySQL 5.6 does not… read-only) transactions. In this case MySQL 5.6 scalability goes back to the good old MySQL 5.5 times and we see identical results with…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
…, 5.6-style buffer pool dump files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6… different implementation in MySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error or diagnostic messages are…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
…, 5.6-style buffer pool dump files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6… different implementation in MySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error or diagnostic messages are…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
… to assertion errors in the log parser or bad changed page data. Bug fixed #1108613 (…#1163439 (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_…(Hrvoje Matijakovic). Release notes for Percona Server for MySQL 5.5.30-30.2 are available in our online…
Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available
… XtraDB Cluster 5.5.30-23.7.4 for MySQL on April 17, 2013. Binaries are available from the downloads area or from our… Fixes: Fixed yum dependencies that were causing conflicts in CentOS 6.3 during installation. Bug fixed #1031427 (Ignacio Nin). In case… in it and on Codership wsrep API 5.5.30-23.7.4, Percona XtraDB Cluster 5.5.30-23.7.4 is now…

