May 25, 2012

Comment: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

… that is derived from that. Essentially, we are using FLUSH TABLES WITH READ LOCK, and then run ‘lvcreate -s’ to create…, we bring up the new mysqld, which finds a crashed innodb, recovers this, and then it is being configured to become… while the recovery of the innodb in the target location fails, though, even though it has been made even under FLUSH TABLES WITH READ…

Post: Recovering Innodb table Corruption

innodb_force_recovery=1 and as you can see even though I get the message in the log file about checksum failing CHECK TABLE says table is OK. This means You Can’t Trust CHECK TABLE in Innodb to be sure your tables are good… data back from simple Innodb Table Corruption. In more complex cases you may need to use higher innodb_force_recovery modes to block purging…

Post: INSERT INTO ... SELECT Performance with Innodb tables.

Innodb tables probably got use to the fact Innodb tables perform non locking reads, meaning unless you …unsafe fore replication and point in time recovery, so use innodb_locks_unsafe_for_binlog option with caution…of MySQL Server) as otherwise the script will fail second time. If you need result to …

Post: MySQL Crash Recovery

… cases – in most cases using Innodb for tables which you need to be recovered fast is better solution. Innodb Recovery – Unless you have some… also mention if you have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables you have, as well as… with Innodb tables, at least not for DDL statements. There is a chance of failing for example during CREATE statement with table created in Innodb

Post: Innodb Recovery Update - The tricks what failed.

… be no way to make Innodb avoid touching it. Even when we dropped all Innodb tables (for test purposes) Innodb still was crashing if… dump tables with innodb_force_recovery=4 was confirmed to be added in 5.0.33, meaning you could not really recover corrupted Innodb tables… have some impact. Innodb tables rarely become corrupt Indeed even if you leave out crashes in my experience Innodb tables become corrupted more seldom…

Post: Using VIEW to reduce number of tables used

tables per server which can become really inefficient. It is especially inefficient with Innodb tables both in terms of space (some tablesInnodb), keeping all tables open in Innodb dictionary and number of other challenges in IO management and recovery

Post: Connecting orphaned .ibd files

innodb_force_recovery doesn’t help Chris Calender suggests two methods. The first is create/drop the tableInnoDB dictionary. It consists of several internal tables. For our topic only SYS_TABLES and SYS_INDEXES are relevant. These are usual InnoDB tables

Post: Using MyISAM in production

…of thousands tables) Innodb was better choice mainly because of thouse other behaviors … well table locks …to keep into account while using MyISAM tables. Recovery. MySQL was running stable for us, …directory. This way accesses to non-checked tables fail with table does not exist error rather than …

Post: Small things are better

… as automatic check on boot failed and had to be manually restarted. Same may happen with Innodb tables. They are designed to never… tables allow per table backup and recovery to happen faster. With MySQL and blocking ALTER TABLE there is yet another reason to keep tables small… add extra column to 500GB Innodb table. It will probably take long hours or even days for ALTER TABLE to complete and about…

Post: Ultimate MySQL variable and status reference list

innodb_status_fileblogpercona.commanual innodb_strict_modeblogpercona.commanual innodb_support_xablogpercona.commanual innodb_sync_spin_loopsblogpercona.commanual innodb_table_locksblogpercona.commanual innodb_thread_concurrencyblogpercona.commanual innodb…commanual rpl_recovery_rankblogpercona….