tscanausa

Absolutely.

For some customer it is the right thing for other customers it may not be the right thing.

Every provider will have failures. So the question mostly boils down to does paying for more then 1 region cost more or less then paying for the the lost productivity or revenue of an outage like this.

From some places the most costly things they spend money on is employees. If your whole company comes to a stop for even 1 hour. It may cost more then the engineering effort for multi zone, multi region or multi cloud for your critical environments.

Terrance here from Google Cloud Support.

There are only 3 things I can say about this situation. 1) These issues are currently unrelated. 2) We learn a lot from these situations. 3) A lot of these types of issues can be mitigated by running in more then 1 region.

I really cant promise that today's situations will never happen again. There are a lot of moving pieces in our system and sometimes there are things outside of Google's control.

GCP Community Slack is a great place to get access to both Googlers and non Googlers using and understanding platform.

I see this was submitted at some point during my night. I cleared my calendar for tomorrow as well and will be available earlier then normal working hours so that we might have a few hours of overlap. -Terrance

Hi,

Terrance here from Google Cloud Support. We're looking into this. Please email me [email protected] and with any bad experiences you have had I will get you answers by EOD PDT. My calendar is clear to answer them all.

-Terrance

Hi, I am not sure you will read this as it's 10 hours after posting. The cloud sql updating both copies sounds like a bug. If you want to email me your case number I can look into it. I know you don't work with GCP anymore but I like to resolve the issue for other users.

Email: [email protected]

Disclosure: I work on gcp support. Not paid to be here.

Sorry to hear about this. I work for our cloud platform support team ( we don't cover firebsse) and this is not the impression we want our customers to get.

We don't want to be calling customers in the middle of their night while they are sleeping. Its not an effective way to resolve issues. We need help identifying when we fall short so we can fix the issues.

Ways to let us know: 1) fill out the survey when your case is closed. We review every survey but less then 1% of cases get the survey filled out. 2) tweet your case id at us and it also goes through our review process 3) email me ([email protected]) and I can correct the problems. 4) GCP slack community has a whole bunch of active Googlers (and the community will flag one us down) if you are having problems with the support team.

Terrance from GCP Support.

If you have problems with our support team send me an email ([email protected]) and I will look into it.

> now that Google seems to have officially closed the book on ever supporting postgresql.

I would be hesitant to say that this is a fact.

Hi!

Terrance from Google Cloud Platform Support here. If you are having any issues interacting with our support team please drop me a line with some case numbers ([email protected]) and I will take a look and try and resolve them.

The author of this article mentioned running a database server on raid 10 local ssds. I would whole heatedly recommend against this. There is no replication on locally ssd ( at all ). If there is a massive hardware failure there are still situations were all the the data on the local ssds can be lost.

( Disclosure: I would for Google Cloud Platform Support and have seen this happen on rare occasions.)

If you have an case ids, where you had terrible service with Google Cloud Platform Support, please send them to me ([email protected]) and I will investigate them.

Best, Terrance

HN is limiting my post rate. So I can't respond to all of you. If anyone would like to chat about reducing customer anxiety or feedback on what you would like to see on this process, you can send me an email and I will respond when I can.

Tscanausa @ Google