Live data from Hacker News

A Google Cloud support engineer solves a tough DNS case

cloud.google.com

71–80 of 283 posts

Re: A Google Cloud support engineer solves a tough DNS case

#71
post #55

That brings up another point. Should the kernel standardize on unsigned scalars completely? How many legitimate use cases are there to use signed scalars in the kernel?

Using unsigned does not generally fix overflow flaws. It just moves the threshold.

Re: A Google Cloud support engineer solves a tough DNS case

#72

Earlier quoted context omitted.

The front-line support is the same as anywhere else. But Google Cloud has really really good second and third line support, if the first tier can't figure it out. And in many cases, it'll get escalated directly to the implementing engineers. In my experience, Google Cloud is better than most organizations about escalating hard issues up to the chain. Admittedly, this happened at a company with substantial spend, and…

How much is “substantial” for gcp to get decent support? Tens of millions/y certainly wasn’t cutting it...

If you weren't getting substantial support at tens of millions/y, your finance team did something deeply wrong when negotiating the contract.

Re: A Google Cloud support engineer solves a tough DNS case

#73

I'm not an expert with AWS or Google Cloud, so I'm interested in knowing: What "level" of customer or SLA do you have to be to get a certain quantity or guarantee of support and troubleshooting? Or is it that if even a free-tier customer points out something that is fundamentally a problem, it will receive attention by certain solutions engineers? Are there $ spending, 20 x (c3.4x.large), or I-pay-you-for-certain-upt…

Here you go: https://cloud.google.com/support#support-plans $250/month/dev is the minimal for phone calls on technical issues, $150k + 4% of GCP spend for 'come running' support. There're more details here https://cloud.google.com/support/docs/procedures#additional_... though they use the old names for the support tiers.

What "dev" or "user" means here ...for example if I run a server serving some HTTP API.

Re: A Google Cloud support engineer solves a tough DNS case

#74
post #22

This is a fun debugging story, but is a great example why servers should be cattle not pets. Having trouble with a VM? Blow it up and get a fresh one. Still having trouble? The provisioning steps are codified, you can walk through them and find the one that causes the issue.

My fleet of machines I was the owner of at Facebook was around 10,000. I still remember the odd JVM crash that prompted me to reimage a machine. I wouldn't have remembered it except there were a few that month and it was the 3rd time I reimaged the same machine that I thought, "That's odd... I think I know that machine name." Checked history, saw the 3 repair jobs I had submitted... RAM was reset, CPU was eventually guessed at as bad.

Cattle is a threshold, but when the same problem keeps coming up it's time to call the vet. http://rachelbythebay.com/w/ has many good examples of this, some submitted and voted up here.

Re: A Google Cloud support engineer solves a tough DNS case

#75
post #17

Google support is basically non existent for customers even spending like 5-10K a month on their platform. Even questions you raise on their Reddit sub go unnoticed. They don't have bunch of people actively trying to solve their customers problem. That said the only time my problems were actually listed to were from BigQuery team. Other than this, I don't think it's possible to get any explanation on a feature from a…

We made an effort to reach out to our regional GCP sales team when we moved to GCP and ended up with an account manager and solutions engineer. They've been very helpful and if we have hard questions, we can ping them. Not a huge spend by any means.

We rarely have to do so, but whenever we did, they went out of their way to figure it out.

YMMV, I guess?

Re: A Google Cloud support engineer solves a tough DNS case

#76

Earlier quoted context omitted.

Here you go: https://cloud.google.com/support#support-plans $250/month/dev is the minimal for phone calls on technical issues, $150k + 4% of GCP spend for 'come running' support. There're more details here https://cloud.google.com/support/docs/procedures#additional_... though they use the old names for the support tiers.

What "dev" or "user" means here ...for example if I run a server serving some HTTP API.

I believe it means "person who wants the ability to contact cloud support".

For small to medium sized businesses, that number is probably 1.

Re: A Google Cloud support engineer solves a tough DNS case

#77
post #62
post #51

Long-term solution - Use rust

Can you expand on your answer. How does Rust resolve this issue? Does it solve by disallowing type casts thereby preventing overflow when the number becomes negative?

I think this person is trolling. However, for the purposes of discussion, two things here:

So, in Rust, overflow panics in debug builds, but does wrap around in release builds. So, it is possible this bug would have been caught in testing, but if it wasn't, it still would have slipped into production.

However, that being said, Rust does not do implicit casting between numeric types. So it's very likely that this code would not have compiled in the first place, though I haven't examined it super closely. At that time, the person would have had to cast it, and so the end result would have been roughly the same.

Re: A Google Cloud support engineer solves a tough DNS case

#78
post #71
post #55

That brings up another point. Should the kernel standardize on unsigned scalars completely? How many legitimate use cases are there to use signed scalars in the kernel?

Using unsigned does not generally fix overflow flaws. It just moves the threshold.

Sure. I was not suggesting it that it will eliminate overflows but would eliminate one source of them. Also mostly because there are probably few use cases that warrant signed values.

Re: A Google Cloud support engineer solves a tough DNS case

#79

I'm not an expert with AWS or Google Cloud, so I'm interested in knowing: What "level" of customer or SLA do you have to be to get a certain quantity or guarantee of support and troubleshooting? Or is it that if even a free-tier customer points out something that is fundamentally a problem, it will receive attention by certain solutions engineers? Are there $ spending, 20 x (c3.4x.large), or I-pay-you-for-certain-upt…

This question brings to mind a recent experience I had with Scaleway support. I pay maybe 25 euro a month to host my k8s based application on their managed k8s offering.I did not pay the extra 2 euro a month for an upgraded support tier. I encountered an issue when deploying istio to the cluster, pinged the scaleway support chat on a saturday, and they had figured out the bug on their end and had a fix eta estimate within a few minutes and had the fix in the next business day. Those guys have fantastic support.

Re: A Google Cloud support engineer solves a tough DNS case

#80
post #17

Google support is basically non existent for customers even spending like 5-10K a month on their platform. Even questions you raise on their Reddit sub go unnoticed. They don't have bunch of people actively trying to solve their customers problem. That said the only time my problems were actually listed to were from BigQuery team. Other than this, I don't think it's possible to get any explanation on a feature from a…

Google isn't bad with commercial accounts through normal channels. I'd personally put them in middle of the road. Their sales/se type people that I've dealt with are above average in my experience, although in the past there weren't many of them.

If you're 5 people at a dentist office with GSuite, that may be a different story. That's always a problem when small entities buy direct -- that's why VARs exist to provide more handholding for smaller orgs.

I've managed some pretty significant vendor relationships -- if you think they are the worst from a support POV, you're young or exceptionally lucky!

Post reply on HN