June 20, 2013

Post: MySQL 5.6: Improvements in the Nutshell

…for multiple table_open_cache instances – Large (over 4GB) redo logs support Optimizer and Execution – Index Condition pushdown (ICP) …information – Optimizer Tracing – Deadlock Logging – GET DIAGNOSTICS Operational Improvements – Separate Tablespaces for Innodb Undo Logs – Fast Restart – Preloading …

Comment: How to estimate time it takes Innodb to Recover ?

Well REDO phase of recovery is completed before MySQL starts to accept connections. Undo phase is in background and is not really visible – you can find it in the error log. Also in SHOW INNODB STATUS you should see undo happening.

Post: What is the longest part of Innodb Recovery Process ?

… part of recovery after crash for Innodb tables could be UNDO stage – it was happening in foreground and was basically unbound… take long hours. REDO stage on other hand always could be regulated by size of your Innodb log files so you could…. Read more about it here. Since MySQL 5.0 the UNDO stage is running in background so it still can be…

Comment: How to estimate time it takes Innodb to Recover ?

… part of recovery after crash for Innodb tables could be UNDO stage – it was happening in foreground and was basically unbound… take long hours. REDO stage on other hand always could be regulated by size of your Innodb log files so you could…