[google-cloud-sql-discuss] Re: Read only flag set automatically, data inconsistency between master/replica.

My advice is to file a production issue on https://code.google.com/p/googlecloudsql/issues/list, and provide as much detail as possible (you can make the issue private) so that we can look into it.

On Saturday, July 16, 2016 at 6:31:30 AM UTC-4, prisms.topscool@gmail.com wrote:

Ok, looks like the read only flags are working fine.
But the master keeps failing randomly and when it goes to failover, I get the The MySQL server is running with the --read-only

According to the docs, when the master fails the replica becomes the new master. Any way to trigger this manually, or figure out why the master is failing?

On Saturday, July 16, 2016 at 3:34:15 PM UTC+5:30, prisms....@gmail.com wrote:

This is for 2nd generation instances

On Saturday, July 16, 2016 at 3:33:18 PM UTC+5:30, prisms....@gmail.com wrote:

Today morning, my SQL instances and replica both were automatically set to read_only ON.

I set the flags manually to off.

Further, I found that there is data inconsistency between replica and master. How do I find out if the connection is broken? How do I restore/sync the master to the replica?

I also created a test instance with a replica and found that read_only was set to ON though the default should be off. Right?

--
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/9bffd46d-f0f9-405c-b6b5-c837eb02cf66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.