Replicated database on a different maintenance schedule?

35 views
Skip to first unread message

Peter Kok

unread,
Mar 12, 2020, 8:16:35 AM3/12/20
to Google Cloud SQL discuss

ink.png


Curious why the replicated database has a different maintenance schedule than the primary database. I really don't want two outages...

If these outages are not synced, at least give me control over the maintenance schedule for the replicated database like I have for the primary!

noverlyjoseph

unread,
Mar 12, 2020, 11:50:07 AM3/12/20
to Google Cloud SQL discuss
While the Master is in maintenance mode, you will be able to access your data from the Read Replica, if both goes under maintenance at the same time you would not have access to your data during that time.

Peter Kok

unread,
Mar 13, 2020, 9:16:07 AM3/13/20
to Google Cloud SQL discuss
Understand that in certain scenario's it's beneficial to have those windows separated, in other scenario's (like mine) it's not. I would be nice I can make that decision for my environment, not something Google decides for me.

David (Google Cloud Support)

unread,
Mar 13, 2020, 6:33:12 PM3/13/20
to Google Cloud SQL discuss

As mentioned previously, the purpose of having different maintenance windows is for still having access to the read replica while the Master is in maintenance. This behavior should be expected behavior, and according to this doc, maintenance windows are not supported by read replicas, and maintenance can happen at any time.


If you would like to have the option to select a maintenance window for read replicas, you can always submit a feature request to possibly get this implemented.

Reply all
Reply to author
Forward
0 new messages