How to stop google cloud sql from corrupting database tables

Question

Today I noticed my wordpress website one GAE-php has no more posts and the logs claim

WordPress database error Table './dbname/wp_posts' is marked as crashed and should be repaired

Some time before that I saw errors in log relating to "duplicate keys", but I can't seem to be able to find exact errors now through log viewer.

• Why are this errors occurring on Google Cloud SQL,
• how can I stop them from happening and,
• is there another option to store this data in a way that will not corrupt tables?

Answer 1

.MYI files indicate to me that you're using MyISAM. Cloud SQL strongly recommends you use InnoDB. Try changing your tables to use InnoDB instead, which the previous link also describes how to do.