Re: Is there any legal case where a clean shutdown leaves crashed MyISAM tables?
Posted by:
Saverio M
Date: February 19, 2014 08:44AM
>> some MyISAM tables are marked as crashed on restart.
> They may have been marked from a previous crash.
> Some such markings are harmless -- as if the table was open when the crash
> occurred. This implies that _something_ failed to be written to disk. That
> flag is cleared on a clean shutdown. If all is quiet before the crash, then
> nothing other than that flag is waiting to be written.
Those tables were clean (and frequently used) before the restart, so definitely there's some problem with writes not happening when shutting down.
>> Is this a MySQL bug, or am I missing something?
>> We've been using several 5.6.x versions.
> Oracle has all but abandoned MyISAM. You really should switch to InnoDB.
> The problems you mentioned will vanish.
Yes, we're working on it; unfortunately, we have fulltext indexes, and until a recent version (5.6.15), InnoDB fulltext indexing had a bug related to savepoints, which made this feature essentially useless.
Subject
Views
Written By
Posted
2737
February 12, 2014 05:03AM
1498
February 13, 2014 11:18PM
Re: Is there any legal case where a clean shutdown leaves crashed MyISAM tables?
1470
February 19, 2014 08:44AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.