0

I have a highly available PostgreSQL instance on google cloud. Also there are some read replicas set for this database.

In case of upgrading the Cloud SQL instance and adding more cores and memory a restart is needed.

What will happen to the Read replicas, will they continue to serve requests as the upgrade takes place? As far as I am aware the read replicas should have the same specs with the original database. Are they going to be restarted and upgraded? If not is upgrading the read replica a manual process?

gkatzioura
  • 2,655
  • 2
  • 26
  • 39
  • 1) AFAIK you cannot vertically resize Cloud SQL with Read Replicas. 2) Read Replicas can be a different machine type. 3) Requests do not failover to a Read Replica. You must manage connections including selecting a different node for requests and/or retrying requests after a delay. – John Hanley Nov 03 '19 at 16:38

1 Answers1

2

What will happen to the Read replicas, will they continue to serve requests as the upgrade takes place?

In case of an upgrade a restart is needed for your CloudSQL master instance, your Read replica will remain untouched and it will continue serving the dedicated requests (different than masters).

What will happen to the Read replicas, will they continue to serve requests as the upgrade takes place? As far as I am aware the read replicas should have the same specs with the original database. Are they going to be restarted and upgraded? If not is upgrading the read replica a manual process?

About Read Replicas specs, master and read replicas must have the same capacity, thus you are only able to change master's capacity which will change also the capacity of the read replicas.

Although this is not the case on the Machine Type (CPU & Memory). You can change CPU and Memory on your read replicas manually as much as you want, but your master instance is able to upgrade memory and CPU until the lower specs of your read replica. So, the master instance is following the smaller read replica.

Take into consideration also Google's documentation for requirements and tips for replication

Noohone
  • 694
  • 5
  • 12