TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

GCP automatically lowered our quota, caused an incident, and refused to upgrade

261 点作者 teej将近 2 年前

23 条评论

yashg将近 2 年前
I keep getting badgered by GCP channel partners to move over to GCP. One guy once said if I can show him our AWS usage he can give me exact configuration in GCP and cost would be 20-25% less. I was intrigued so I shared. He came back with a price estimate higher than our AWS bill! I haven't entertained them ever since.
评论 #36274528 未加载
评论 #36275109 未加载
评论 #36277024 未加载
Demmme将近 2 年前
Just an anecdotal counter point: very happy with gcp.<p>Best network from all and coherent modern ui.<p>Not the usability hell like azure... (You know when clicking on a often used resource on the start page which let&#x27;s you jump directly to it but doesn&#x27;t allow you to jump a level up of all the other resources of the same type which totally works fine when you navigate to it the normal way... Or the huge hassle and complexity of resource groups for f everything...)<p>But you know the tweet not even states what quota was reduced.
评论 #36276424 未加载
评论 #36275372 未加载
评论 #36275144 未加载
评论 #36276950 未加载
评论 #36278268 未加载
评论 #36275512 未加载
评论 #36279603 未加载
评论 #36274304 未加载
评论 #36274701 未加载
redman25将近 2 年前
We had a similar thing happen with our company. Google had given a bigquery concurrent query limit extension to 300 queries. In January they removed the extension back down to 100 concurrent queries because they were introducing “query queues” that should cover the difference.<p>Unfortunately for us, query queues only affect spikes in concurrent queries and not overall throughput. We’ve been struggling with bigquery support ever since.
评论 #36275891 未加载
parpfish将近 2 年前
I’ve recently had an issue where GCP keeps shutting down my e2.micro because they think I’m crypto mining. I have no idea what I’m doing to trigger it, and I don’t blame them for not sharing their secret anti fraud heuristics, but it’s a freakin e2.micro. They think I’m mining on that?!
评论 #36277217 未加载
评论 #36274319 未加载
评论 #36292380 未加载
crescentfresh将近 2 年前
Anecdotally, I know a paying GCP customer that recently got quota blocked on the number of global static IPs they are allowed to create. We could not figure out how to contact someone to increase it, and nobody knew why the quota was set so low (4). We just kept running into automated systems that gave circular information on how to request an increase. We kept getting links to sign up for a free tier account.
评论 #36276494 未加载
评论 #36276353 未加载
robin_reala将近 2 年前
There was a follow-up Tweet that “explains” the problem:<p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;JustJake&#x2F;status&#x2F;1667492928758095872" rel="nofollow noreferrer">https:&#x2F;&#x2F;twitter.com&#x2F;JustJake&#x2F;status&#x2F;1667492928758095872</a><p>From the call with Google just now:<p>Them: &quot;You exceeded the rate limit&quot;<p>Us: &quot;We did 5000&#x2F;10min. The quota was approved at 18k&#x2F;min&quot;<p>Them: &quot;That&#x27;s not the rate limit&quot;<p>Us: &quot;What&#x27;s the rate limit&quot;<p>Them: &quot;Not sure have to check with that team&quot;<p>So, the quota is completely cosmetic...
holografix将近 2 年前
A friend works at GCP and has told me this time and time again: if you don’t buy support from GCP _you have no support_.
评论 #36275597 未加载
评论 #36276995 未加载
willtemperley将近 2 年前
I had to close my GCP account because I was being spammed with &quot;Action Required&quot; emails every day for a non-existent tax admin issue. Bug reports were immediately closed and getting through to a human seems impossible.
jtchang将近 2 年前
Why don&#x27;t I hear about these incidents with AWS? Is it just less common or different business takes on quotas and rate limits?
评论 #36273607 未加载
评论 #36273797 未加载
评论 #36273598 未加载
评论 #36274071 未加载
评论 #36274334 未加载
评论 #36275086 未加载
ineedasername将近 2 年前
Hilariously reminiscent of Kafka:<p>Client: we were under the limit<p>GCP: No, you exceeded the limit<p>Client: Then what is the limit?<p>GCP: I don’t know
endisneigh将近 2 年前
Tweet has basically no details
评论 #36274324 未加载
invalidname将近 2 年前
From my past experience Google is by far the worst when it comes to support. By far. Even if you pay for their gold support you&#x27;re lucky if you reach an engineer and even then they blame you for the problem with no &quot;proof&quot; or direction. Most unhelpful ever... See: <a href="https:&#x2F;&#x2F;medium.com&#x2F;hackernoon&#x2F;why-and-how-we-left-app-engine-after-it-almost-destroyed-us-40ac2fc0b1a8" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;hackernoon&#x2F;why-and-how-we-left-app-engine...</a><p>AWS were surprisingly helpful by comparison and even pro-active. Not a fan of theirs overall but much better than Google. This is a deep cultural problem with Google that also expresses itself in mobile development and everywhere: <a href="https:&#x2F;&#x2F;dev.to&#x2F;codenameone&#x2F;google-play-kafkaesque-experience-mp3" rel="nofollow">https:&#x2F;&#x2F;dev.to&#x2F;codenameone&#x2F;google-play-kafkaesque-experience...</a><p>They aren&#x27;t the cheapest and their service is terrible. I can&#x27;t think of a good reason to use GCP.
评论 #36273800 未加载
评论 #36276123 未加载
评论 #36274169 未加载
评论 #36273780 未加载
评论 #36275701 未加载
klodolph将近 2 年前
In my limited experience, quota is one of the pain points of GCP. It&#x27;s where the cloud &quot;leaks&quot;.
mvdtnz将近 2 年前
Quota for what?
评论 #36283194 未加载
kaliszad将近 2 年前
One thing I don&#x27;t understand is how in 2023 people use GCP with the bad level of IPv6 support they have. Other Google services usually support IPv6 quite well. Only GCP, to some degree Chromecast, probably Nest and the DHCPv6 problem of Android are some well known exceptions.<p>Google also tend to put algorithms first and people and their business second so that is why I would be very particular about using GCP for anything serious. We do use Google Workspace and for what we do with it, it is mostly ok, however rather expensive.
aledalgrande将近 2 年前
I&#x27;ve never used GCP for anything but demos, but on the other side AWS support is worth the (high) price: I always had my issues solved, quickly, and sometimes I was even able to put in feature requests that were shipped a few weeks later.
profwalkstr将近 2 年前
It feels as if Google is intentionally trying to sabotage its own cloud business
Animats将近 2 年前
Google giveth, and Google taketh away. Blessed be the name of Google.
评论 #36273493 未加载
pawelduda将近 2 年前
Wonder what does GCP side have to say on this
评论 #36273562 未加载
评论 #36273770 未加载
uoaei将近 2 年前
It is interesting to note the differences in apparent defensibility of companies such as Google and Reddit changing terms of use and behaviors of platforms.<p>According to the general sentiment on HN, Google is being mean to developers and shouldn&#x27;t get away with things like this, but Reddit merely has a rug and developers are silly to build things on top of that rug when it can be pulled away at any time.<p>I wonder why there&#x27;s a difference here.
评论 #36275483 未加载
exabrial将近 2 年前
Once Again: Do not use Google for anything. Given they treat the consumer side of their business like cattle (Gmail, maps, etc) (,and despite the fact that an email address is an essential part of one&#x27;s daily life: access to banking, investments, communication, cell phone, employment opportunities), they operate with absolutely zero support.<p>What makes you think they&#x27;ll treat your small business any differently? You will be thrown under the bus the second you make them lift a finger to help you.
评论 #36276802 未加载
nathants将近 2 年前
the purpose of not aws is two:<p>- put price&#x2F;quality pressure on aws<p>- fill weird niches made by regulatory capture and other nonsense<p>not using aws is like not using linux. there are valid reasons, but you don’t want any of them.
评论 #36275826 未加载
评论 #36277458 未加载
showdeddd将近 2 年前
This article seems silly, just add custom metrics to your app for what was fetched from cache vs DB. And label the metric by route&#x2F;query&#x2F;pattern. To control costs, don&#x27;t tick the metric for every single request, instead accumulate locally and post to metrics API every X minutes.