…we always could repair table by running ALTER TABLE with limited impact to production system (as only one table of about …now dump potentially corrupted tables (in this particular corruption instance Innodb did not print table name in question), drop tables, restart Innodb without innodb_force_…
Post: Using MyISAM in production
June 17, 2006 By 36 Comments
… rows in tens of thousands tables) Innodb was better choice mainly because of thouse other behaviors … well table locks was the problem at… way accesses to non-checked tables fail with table does not exist error rather than wait forever. Hidden corruptions. If could be bad… sync and if you do not repair the table you will very likely observe very serious corruption with queries failing to run, wrong…
Post: MySQL Crash Recovery
July 30, 2006 By 30 Comments
…corrupted tables may be reason for further crashes or hangs, and corruption may spread itself further in the table…different queries which may trigger check/repair running for many tables at onces, which typically…have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables …
Comment: Should you move from MyISAM to Innodb ?
January 12, 2009 By 59 Comments
… single table parsing. In that case, I suspect you will certainly NOT have the time for a REPAIR TABLE on your MyISAM’s corrupted table…. On average, 5 days each week are consumed by REPAIR TABLE. The larger tables take 4-5 *days* to restore. Please be prepared… comment #18. If the above sounded like a “always use InnoDB” preach, that was not my intent. I was merely trying…
Post: Small things are better
October 8, 2006 By 15 Comments
… repairing took many hours especially as automatic check on boot failed and had to be manually restarted. Same may happen with Innodb tables. They are designed to never crash, surviving power failures and even partial page writes but still they can get corrupted…
Comment: Should you move from MyISAM to Innodb ?
December 20, 2012 By 59 Comments
I am afraid of Innodb corruption since from time to time the computer goes offline (due power failure or other reasons). I’ve read that it sucks when Innodb get corrupted, while MyISAM tables can be repaired with REPAIR table .
Post: Monty unviels Maria and starts Blogging
January 29, 2008 By 4 Comments
…and row level locks functionally close to Innodb or Falcon. Though many internal architecture decisions… check and repair tables from the very first versions as well as has tables movable between the… data in theory never is corrupted and database maintains consistency between tables so you should not…
Comment: MySQL Northern European Customer Conference
October 17, 2007 By 7 Comments
… Bugs on Primary can corrupt storage… which will be replicated by DRBD – Long switch time even for Innodb tables – on large system tuned… performance. – Pretty much unusable for MyISAM tables which may take infinity to check and repair – Waste of hardware as Secondary node sits…
Comment: Should you move from MyISAM to Innodb ?
January 12, 2009 By 59 Comments
…’m curious how you’re dealing with repairing of these MyISAM tables or are you switching to the … slave or DRBD/SAN based standby 2) Data corruption with crash. Switch to the slave. 3) Hacker … we would have recommended you to stay with Innodb reviewing your application. Just recognize it is not …
Comment: MySQL Crash Recovery
October 12, 2007 By 30 Comments
gigiduru, If MySQL crashed in your case that is a but and it does not normally happen. Regarding MyISAM locking and corruption it is a choice – if you want want table locks and repair after server crash you go with MyISAM if you want transactions and multi versioning you go with Innodb.
