MENU
You manage a meeting booking application that uses Cloud SQL. During an important launch, the Cloud SQL instance went through a maintenance event that resulted in a downtime of more than 5 minutes and adversely affected your production application. You need to immediately address the maintenance issue to prevent any unplanned events in the future. What should you do?
36 comments · newest first
RH
Rhea
10 months ago
Wait, can you really schedule a maintenance window for only 5 minutes?
RO
Rose
10 months ago
I disagree, migrating to Cloud Spanner could be a better long-term solution.
MI
Milly
11 months ago
Definitely need to contact Support about that downtime!
TA
Tamesha
11 months ago
Non-business hours maintenance is a must to avoid disruptions!
DO
Dolores
11 months ago
Setting the maintenance window to non-business hours seems smart.
JO
Joseph
11 months ago
I practiced a question about using Cloud Scheduler, but I’m not sure if scheduling a maintenance window of just 5 minutes is enough to cover all scenarios.
LE
Leonora
11 months ago
I think contacting support could help clarify what went wrong, but it might not be a long-term solution.
MA
Margart
12 months ago
I'm not entirely sure, but migrating to Cloud Spanner sounds like a big step. Would that really prevent future maintenance issues?
NA
Nathan
12 months ago
I remember we discussed setting maintenance windows during non-business hours to minimize impact. That seems like a practical approach.
DE
Deeanna
1 year ago
Contacting support to understand the root cause of the downtime is a good idea, but it doesn't directly address the issue at hand. I'll need to consider the other options more closely.
TA
Talia
1 year ago
Okay, I think I've got this. Setting the maintenance window to non-business hours seems like the most logical solution to prevent future disruptions. I'll go with that.
FI
Fidelia
1 year ago
Hmm, I'm a bit unsure about this one. Migrating to Cloud Spanner seems like a big change, but I'm not sure if that's the best approach here. Let me think through the other options more carefully.
TO
Tomoko
1 year ago
This seems like a straightforward question about addressing a maintenance issue with a Cloud SQL instance. I'll carefully consider the options and choose the best solution.
JO
Joaquin
1 year ago
Wait, so the Cloud SQL instance went down for more than 5 minutes? That's like trying to run a meeting booking app on a toaster oven. Might as well just use carrier pigeons!
LA
Laticia
1 year ago
Wait, so the Cloud SQL instance went down for more than 5 minutes? That's like trying to run a meeting booking app on a toaster oven. Might as well just use carrier pigeons!
GR
Gregoria
1 year ago
C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
CH
Chau
1 year ago
A) Set your production instance's maintenance window to non-business hours.
MA
Mari
1 year ago
Using Cloud Scheduler to limit the maintenance window to 5 minutes? That's like trying to fit an elephant in a shoebox! Good luck with that one.
JA
Jackie
1 year ago
Using Cloud Scheduler to limit the maintenance window to 5 minutes? That's like trying to fit an elephant in a shoebox! Good luck with that one.
JE
Jess
1 year ago
C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
RE
Ressie
1 year ago
A) Set your production instance's maintenance window to non-business hours.
MA
Malcolm
2 years ago
Contacting Support is definitely the way to go. They should be able to provide insights and help me address this issue.
TA
Tanja
1 year ago
C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
GE
Georgiann
1 year ago
A) Set your production instance's maintenance window to non-business hours.
ME
Mertie
2 years ago
I'm not sure, maybe we should also contact Support to understand why it happened in the first place.
BR
Brett
2 years ago
Migrating to Cloud Spanner seems like an overkill. I'd rather just work with Support to understand the root cause and prevent future disruptions.
NA
Nan
2 years ago
I agree with Timmy, that seems like the best option to prevent future downtime.
ME
Mee
2 years ago
Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.
CH
Charlene
1 year ago
That's a good point. I should definitely reach out to Support to investigate the downtime issue.
LO
Loreta
1 year ago
C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
JE
Jeannetta
1 year ago
Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.
SA
Sage
1 year ago
A) Set your production instance's maintenance window to non-business hours.
KI
Kizzy
1 year ago
Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.
LA
Lavonne
1 year ago
C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.
FL
Fletcher
1 year ago
A) Set your production instance's maintenance window to non-business hours.
TI
Timmy
2 years ago
I think we should set the maintenance window to non-business hours to avoid disruptions.