“Over quota” when using GCS json-api from App Engi

2019-05-11 04:52发布

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?

2条回答
何必那么认真
2楼-- · 2019-05-11 05:24

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

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.

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.

查看更多
迷人小祖宗
3楼-- · 2019-05-11 05:32

Even i had found same problem and found two reasons:- 1.Daily budget 2.Logs retention

Solution: for problem 1 increase the daily budget for problem 2 increase the retention from 1 to higher GB ![enter image description here][1]

查看更多
登录 后发表回答