Q: - during the primary instance maintenance windows, is the standby instance also being upgraded?
A: Maintenance done on the CloudSQL Instances are not done at exactly the same time. However, from sample instances that I checked, it seems the maintenance on Failover Instances is done just a few minutes apart from the Maintenance on the Primary Instance.
Q: - if it's not, does it make sense to initiate manually failover right before the maintenance to the standby instance to prevent downtime? is it doable?
A: Considering my response above, it may not be advisable to trigger the failover right before the maintenance on the primary instance as the Maintenance process may be done a few minutes apart.
While triggering your failover Instance before the Maintenance on primary instance may be doable, there are a number of factors that may apply. For example, how to determine exactly when the maintenance would take place(Maintenance window only allows for specifying a time window).
I'd rather you carefully review your planned maintenance Window to minimize the impact on your application. Better still, you can setup a Read replica[1] which would ensure that read operations can still be completed during the down time imposed by the maintenance. Checking samples instances on my end, I observed that the maintenance on Read replicas seem to be done only after the completion of the maintenance on Failover and primary Instances.
[1]https://cloud.google.com/sql/docs/mysql/replication/tips/#read-replica
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/9d7c9e5b-4718-42e2-9149-b42869bdd0f4%40googlegroups.com.
No comments:
Post a Comment