“超出配额"从App Engine使用GCS json-api时 [英] "Over quota" when using GCS json-api from App Engine

问题描述

我在App Engine上使用Go.在大多数情况下，我使用文件api 进行访问GCS很好用，除了删除不起作用为了删除文件，我使用JSON-API(具体来说， google-go- api-client ).为了进行身份验证，我使用了应用引擎服务帐户.有时我们会看到超出配额:"错误返回，冒号后面没有任何内容.由于我们是付费应用程序，这可能是多少配额?是否有突发次数限制(例如，一分钟内不超过X个请求)?是否在任何地方记录了此类适用的配额?

I am using Go on App Engine. In most cases, I use the file api to access GCS, which works great, except that deletes don't work so to delete files I use the JSON-API (specifically, the google-go-api-client). To authenticate, I use app engine service accounts. We are sometimes seeing an error come back of "Over quota:" with nothing after the colon. Since we are a paid app, what quota could this be? Is there a burst limit (e.g. no more than X requests in a single minute)? Is there any places where any such applicable quotas are documented?

推荐答案

goauth2和serviceaccount令牌的缓存机制已中断.您可以在这里看到我创建的问题的更多详细信息: https://code .google.com/p/goauth2/issues/detail?id = 28

The caching mechanism is broken for goauth2 and serviceaccount tokens. You can see the issue I created here for more detail: https://code.google.com/p/goauth2/issues/detail?id=28

我每分钟请求60个以上的服务帐户时遇到了一个超额配额"问题.我在AppEngine支持下开了一张票(我为银牌包付钱)，并从他们那里得到了这些未记录的信息.

I came across a "over quota" issue myself when requesting more than 60 service accounts a minute. I opened a ticket with AppEngine support (I pay for the silver package) and got this undocumented information out of them.

您可以在$ GOPATH/src/code.google.com/p/goauth2/appengine/serviceaccount/cache.go文件中自行应用补丁.这解决了您为我的团队描述的问题.

You can apply the patch yourself in your $GOPATH/src/code.google.com/p/goauth2/appengine/serviceaccount/cache.go file. This fixed the issue you described for my team.

这篇关于“超出配额"从App Engine使用GCS json-api时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！