… was dropped and innodb_file_per_table is ON Frm file corrupt, zeroed out, lost or SHOW CREATE TABLE crashes MySQL There is yet another source of information about the table structure – InnoDB dictionary. Let’s review… is still zero. If you know how InnoDB uses `PREC` please let me know. mysql> select * from SYS_COLUMNS WHERE TABLE_ID…
Post: Is Synchronous Replication right for your app?
… after a crash, it has to get to disk. This has no effect on standard MySQL replication from this instance, since MySQL replication… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to… to the tradeoffs we take when deploying conventional stand-alone MySQL Innodb with asynchronous slaves. We may not think about the tradeoffs…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
… MySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb…). Percona Server for MySQL was built with YaSSL which could cause some of the programs that use it to crash. Fixed by… the MySQL client because the help tables were missing. Bug fixed #1041981 (Alexey Bychko). Fixed the upstream bug #68197 that caused InnoDB…
Post: Percona XtraBackup 2.1.0 'release candidate' for MySQL available for download
… XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5.6. Starting with MySQL 5.6 buffer pool dumps… on MySQL and Percona Server 5.6 as described in Exporting and Importing Tables guide. Bugs Fixed: Percona XtraBackup would crash when… different implementation in MySQL 5.6 error messages were not printed to stderr directly. Because of that all InnoDB error or diagnostic…
Post: MySQL Crash Recovery
… penalty. If using Innodb you also might with to use innodb-safe-binlog option in MySQL 4.1 so your Innodb log and binary log are synchronized. In MySQL 5.0… problems which you may experience related to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb tablespace recovery etc but I should write…
Post: No more MySQL Crash Safe Replication in 5.0 ?
… if you’re only using Innodb tables your replication is not completely crash safe – if Slave MySQL Server crashes/power goes down it is… MySQL 4.0 and 4.1 series there was a great workaround if you’re using only Innodb tables – Innodb when Innodb does crash recovery it would print position in master log files up to which replication was done: InnoDB: In a MySQL…
Post: Feature in details: Incremental state transfer after a node crash in Percona XtraDB Cluster
… after a crash. This feature was available even in previous release, but now I want to give some details. So, MySQL crashes from… question: if mysqld crashes, how do we know what is the last transaction was executed. For a single InnoDB instance it is…, we store GTID in InnoDB system area, which is updated for each transaction. So even the system crashes, we can access information…
Post: How InnoDB handles REDO logging
… InnoDB cannot log at all, your transaction will never complete. Both the MySQL configuration and hardware will affect the speed at which InnoDB can log. You can request that InnoDB force its REDO… the event of a MySQL crash the data will still be consistent, however in the event of a system crash there may be…
Post: Recovering Innodb table Corruption
… problem is there is some buffering taking place and as MySQL crashes it does not store all data it could recover to… instead make sure to use LIMIT or PK Rangers when MySQL crashes you will not get all data in the network packet… after MySQL crashes to make sure indexes are not corrupted. So we looked at how to get your data back from simple Innodb…
Post: Percona Testing: Innodb crash / recovery tests available
Not everyone may know this, but there are precious few innodb crash recovery tests available. Some folks have noticed this and asked… unfortunately, no tests have been created for the main MySQL branch. The MySQL at Facebook branch has a number of tests that… written to take advantage of this (like our shiny new Innodb crash tests!), it is very easy to shuffle data and queries…

