[google-cloud-sql-discuss] Re: MyISAM tables on Cloud SQL

Bingo - I think you definitely found the problem.  I'd neglected to mention that my original instance allowing MyISAM had a failover instance, and at one point awhile ago, I know I tested it by triggering a failover (never crossed my mind that it may be relevant).  So yes, the instance that allows MyISAM engines was once a failover instance that was promoted to a master.

At least if you were able to now duplicate this unexpected behaviour, it should be easier for the Cloud SQL team to track down and fix.  Presumably when a failover or read replica are configured, it may not be done with the same flags as a master prohibiting tables other than InnoDB (which of course, since they are read only when accessed directly, wouldn't be noticed unless a failover is promoted to master).

In any case, I'll certainly make sure my tables are manually converted to InnoDB - the behaviour of allowing a MyISAM engine is definitely unintentional, and likely won't survive when they patch this.

Thanks for helping to troubleshoot this!

Dan

On Sunday, May 27, 2018 at 12:43:28 PM UTC-6, Fady (Google Cloud Platform) wrote:

Hello Dan,

I found it odd that on your existing instance, you initially were not able to use myISAM, but then somehow that changed. So a possible explanation for this behavior could be that you had configured your instance for high availability, and the replica itself may had this issue and not the original master. Hence, the failover instance (due to failover) could have replaced the original master (became master and retained the original master's ID). [Side note] The procedure also creates a new failover instance to replace the old failover.

That said, I tested this theory and found that when the failover instance replaces the master, it indeed allows using myISAM, and that is not an expected behavior. Thus, I opened this public issue for further investigation by the Cloud SQL team. If that is not the case with you, you may open a private issue per my suggestion above to inspect your instance.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/81555b1e-dc8e-4f60-879e-4f73d3d353c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.