May 25, 2012

Comment: How to change innodb_log_file_size safely

… 11:51:16 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer…

Comment: How to recover a single InnoDB table from a Full Backup

… 6087296438643. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for…

Post: Troubleshooting MySQL Memory Usage

… *************************** SESSION_ID: 7234 TABLE_SCHEMA: test TABLE_NAME: my ENGINE: InnoDB NAME: #sql516_1c42_2 TABLE_ROWS: 0 AVG_ROW_LENGTH…) File system 294352 (82672 + 211680) Lock system 318875832 (318747272 + 128560) Recovery system 0 (0 + 0) Threads 425080 (406936 + 18144) Dictionary memory…

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

….mysql.com with details from the mysqld error log? AFAIK, InnoDB is snapshot safe as long as database files and log files are on the same filesystem. But MySQL/InnoDB is not snapshot safe if DDL operations are in flight… (frm files) and InnoDB is not atomic and some failures are not recoverable (which can cause problems for recovery after a snapshot…

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

…, we bring up the new mysqld, which finds a crashed innodb, recovers this, and then it is being configured to become… the donor machine. Every once in a while the recovery of the innodb in the target location fails, though, even though it…

Comment: Connecting orphaned .ibd files

… file a bug here https://bugs.launchpad.net/percona-data-recovery-tool-for-innodb

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

… be recoverable 100% of the time. You might have found recovery bug but there have been very few of them. Typically… on the same partition or synchronization of binary log and innodb snapshot. In certain versions FLUSH TABLES WITH READ LOCK would…

Comment: Percona Server vs MySQL on Intel 320 SSD

Patrick, There are two factors: 1. Speed of recovery is much better in MySQL/Percona Server 5.5 2. Having on SSD makes it also much faster. So having big log files is practical under these conditions. It still may be long, but that that painful as in old InnoDB.

Post: How innodb_open_files affects performance

… 18:43:36 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… InnoDB: Doing recovery

Post: Copying InnoDB tables between servers

…:22:43 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Doing recovery: scanned up to log sequence number 3 768598528 (6 %) …. InnoDB: Doing recovery