…. Bug fixed #907499 (Ignacio Nin). Crash-resistant replication would break with binlog XA transaction recovery. If a crash would happened between XA PREPARE and COMMIT stages, the prepared InnoDB transaction would not have the slave position recorded and thus would fail to update it once it is replayed during binlog crash recovery. Bug fixed…
Post: Percona XtraDB Cluster reference architecture with HaProxy
June 20, 2012 By 63 Comments
…=/usr/lib/libgalera_smm.so datadir=/var/lib/mysql wsrep_slave_threads=2 wsrep_cluster_name=pxctest wsrep_sst_method=xtrabackup wsrep_node_name=ip-10-112-39-98 log_slave_updates innodb_locks_unsafe_for_binlog=1 innodb_autoinc_lock…] Recovering after a crash using mysql-bin 120619 13:21:19 [Note] Starting crash recovery… 120619 13:21:19 [Note] Crash recovery finished. 120619 13…
Post: Announcing Percona Server 5.1.66-14.2
January 15, 2013 By Leave a Comment
… #917942 (Mark Callaghan, Laurynas Biveinis). Crash-resistant replication would break with binlog XA transaction recovery. If a crash would happened between XA PREPARE and COMMIT stages, the prepared InnoDB transaction would not have the slave position recorded and thus would fail to update it once it is replayed during binlog crash recovery. Bug fixed…
Comment: Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs
September 29, 2012 By 3 Comments
… data replicated from a active master(M) by doing stop slave in standby(S1) to create new standby server(S2) like… approach but while starting the S2 it goes to INNODB crash recovery & takes long time to start. How to over come this…
Comment: How fast is FLUSH TABLES WITH READ LOCK?
April 24, 2010 By 30 Comments
… does crash recovery it prints the binary log position. This unfortunately does not work if you are backing up from the slave. You…
Post: My "hot" list for next InnoDB features
March 30, 2009 By 18 Comments
… see soon: Fast recovery. Both recovery after crash and recovery from backup can take unacceptable long time, especially if you crashed with full 32GB buffer… if you put load on slave which is not warmed up properly – slave may never catch up slave, but with small load warm…) restore single table from backup, possibly on different server (different slave). It’s all about time – copying whole 500GB backup while…
Post: Using MyISAM in production
June 17, 2006 By 36 Comments
… using MyISAM tables. Recovery. MySQL was running stable for us, giving us false sense of security but when it crashed (or was… careful with myisam_recover. This is great option to automate recovery but it can give you couple of nice surprises. First… always available. For example statistical data. Data on slave servers. If it crashes you can simply re-clone it. Make sure however…
Post: MySQL Backup tools used by Percona Remote DBA for MySQL
March 13, 2013 By 8 Comments
…mysql shuts down Your server or RAID controller crashes and all data is lost on that …can perform point in time recovery. Store your binlogs offsite for disaster recovery scenarios. Run pt-table-checksum …syncing the frm files. Enable –slave-info when backing up from a slave so you know what the…
Post: MySQL Replication vs DRBD Battles
April 28, 2008 By 12 Comments
… take your database to do transactional log recovery is invisible until you get a crash, meaning if your production database size growths… is a hot standby, it’s just not a running slave node from the database’s standpoint. And, nothing stops you… do point in time recovery or to catch up to last few not committed transactions on the slave. We should spend some…
Post: Announcing Percona Server for MySQL version 5.5.29-30.0
February 26, 2013 By Leave a Comment
… fixed #1017192 (Sergei Glushchenko). The server could crash when executing an INSERT or UPDATE statement… causing a memory leak on a filtered slave. Bug fixed #1042946 (Sergei Glushchenko). Percona Server… tracking wasn’t compatible with innodb_force_recovery=6. When starting the server log tracking…
