… focused on MySQL 5.6 GTIDs. You can find part one here. Our goal will be to go from setup #1 to setup…_auto_position=1; s0> start slave; # For s1, s3 and s4 mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave… care if you don’t want to break replication or corrupt your data. Scenario #2: One of the slaves is behind Now…
Post: Migrating between MySQL schemas with Percona Xtrabackup
June 10, 2013 By 2 Comments
…need to compare their old data to their current data on the current live … mysql orig_old < /tmp/orig.schema.sql Ensure innodb_import_table_from_xtrabackup = 1 …you to compare and restore values (potentially corrupted via user error or other issues… my test VM: Percona Server 5.5.30 Xtrabackup 2.0.6 …
Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)
April 17, 2013 By 2 Comments
… of data corruption. MySQL provides the handy RESET SLAVE command. But as we’ll see, its behavior has changed along with the MySQL versions… 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… 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…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
…MySQL version 5.5.30-30.2[/caption] Percona is glad to announce the release of Percona Server for MySQL 5.5…automake 1.12. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_… used with –innodb-optimize-keys and –no-data options, all secondary key definitions would be…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… automake 1.12. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table…was used with –innodb-optimize-keys and –no-data options, all secondary key definitions would be …(Hrvoje Matijakovic). Release notes for Percona Server for MySQL 5.5.30-30.2 are available in our …
Post: How to recover table structure from InnoDB dictionary
April 22, 2013 By 4 Comments
…is ON Frm file corrupt, zeroed out, lost or SHOW CREATE TABLE crashes MySQL There is yet …recovery tool bzr branch lp:percona-data-recovery-tool-for-innodb 1. Compile the dictionary parsers make …STARTING BY ‘SYS_FIELDS\t’ (`INDEX_ID`, `POS`, `COL_NAME`); 5. Now everything is ready to generate a …
Post: Announcing Percona Server 5.1.65-14.0
September 4, 2012 By Leave a Comment
… Percona Software Repositories). Based on MySQL 5.1.65, including all the bug fixes in it, Percona Server 5.1.65-14.0 is now…, lost data due to some rows being updated rather than inserted) with the default value of innodb_autoinc_lock_mode=1. Bug… glibc detected memory corruption. Bug fixed #915814 (George Ormond Lorch III). If the tablespace has been created with MySQL 5.0 or older…
Post: Data Corruption, DRBD and story of bug
November 29, 2010 By 6 Comments
… corrupts data by itself Now to bug 55981. It has MySQL version 5.6, but the problem exists in MySQL 5.1.50 or below and in MySQL 5.5… recommend to upgrade to MySQL version 5.1.51+ . Now another interesting point – how can you be sure that 5.1.51 works. The bug… 5.1.52. However if you look into source code and revision history, you can see that bug 55543 is fixed in MySQL 5.1…
Post: Announcing Percona Server for MySQL version 5.1.67-14.4
March 8, 2013 By Leave a Comment
…MySQL version 5.1.67-14.4 on March 8, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1…, would result in a heap corruption. Bug fixed #1111226 (Laurynas Biveinis)…. Biveinis). InnoDB monitor was prefetching the data pages for printing lock information…
Post: Replication checksums in MySQL 5.6
February 15, 2013 By 3 Comments
MySQL 5.6 has an impressive list of improvements. Among them, replication …] {msandbox} ((none)) > create database sakila; Query OK, 1 row affected (0,00 sec) and corrupt the relay log (I changed sakila to… read from ‘./mysql-bin.000001′ at 2896.’ Conclusion You should not assume that replication checksums in MySQL 5.6 will ensure data integrity in…
