How to avoid longtime MyISAM recovery after MySQL crash or unexpected shutdown

Question

We are using MySQL 5.x for our system, It generates huge amount of data per day. Yesterday at one our customers place, UPS shutdown and after that Mysql start MyISAM recovery that took about 10 hours. Now my question, is there any way to avoid this longtime recovery next time? For example, do something end of day which after next crash only recover from first of day. Or end of day saves data and after that if system crashed nothing happen for last days datas and they don't need recovery.

I'm only starting an idea... partitionned tables, maybe only the last one will need recovery on crash? — Alexandre Lavoie, Dec 23 '12 at 19:16

score 1 · Answer 1 · answered Dec 23 '12 at 19:36

1

Don't use MyISAM. It's an inherently flawed format which is prone to this sort of issue.

Use InnoDB instead. Along with having better recovery behavior, it is also faster under load, and supports transactions.

answered Dec 23 '12 at 19:36

There can be many legitimate reasons for using MyISAM tables and you can have good results with them if you are skillful with them. To avoid long recoveries on crash split your tables into smaller parts. – Sasha Pachev Oct 09 '15 at 20:19

How to avoid longtime MyISAM recovery after MySQL crash or unexpected shutdown

1 Answers1