Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect "insufficient tokens for quota group and limit" error? #1756

Closed
1N50MN14 opened this issue Oct 28, 2016 · 6 comments
Closed

Incorrect "insufficient tokens for quota group and limit" error? #1756

1N50MN14 opened this issue Oct 28, 2016 · 6 comments
Assignees

Comments

@1N50MN14
Copy link

Apologies if this is not really an issue, searched all closed/open issues and on the net, still can't figure it out.

PubSub is throwing the following error:
`Insufficient tokens for quota group and limit 'administratorCLIENT_PROJECT-100s' of service 'pubsub.googleapis.com', using the limit by ID 'XXX'``

I went through the quota usage in the Dashboard for pubsub and I'm way below the limit on all of them, this is not even running in production.

Any ideas what this might be? I know that I generate random subscription ids to ensure messages are received by all subscribers, could this be the cause?

Thanks

Environment details

  • OS:Ubuntu 16 / Docker
  • Node.js version: 4.6.1
  • google-cloud-node version:0.43.0
@1N50MN14
Copy link
Author

closing

@MuthuD
Copy link

MuthuD commented Nov 21, 2016

I'm facing the same issue at times. Not sure about the root cause. Can any one guide me on this?

Thanks in advance

@astroyang
Copy link

Hej @1N50MN14 We have similar problem while our usage is way below quota, we still receive this error. Can you please provide some hints about how you find the root cause? Thanks!

@1N50MN14
Copy link
Author

@astroyang I was giving each subscription a unique subscription name (uuid) to ensure messages arrive to a single subscriber at a time, so one way to reduce usage is to avoid that and instead ignore irrelevant messages. But the main thing that solved it was increasing the quota in the developer console if I remember correctly the default quota is 1K, I took it up to the maximum (10K); it wasn't clear you could actually do that from the console. Finally, I'm now using a different messaging queue for few reasons one of which I I thought 10K was too little - that did it ;)

@astroyang
Copy link

@1N50MN14 Thanks for your kind reply! It seems not exactly the same as our problem but I agree that 10K may seems not enough if you have a relatively active application! :)

@sx5640
Copy link

sx5640 commented May 8, 2017

I ran into the same issue as well. In my case it was Administrative operations that limited the number of requests. It is set to 1,000 per 100 seconds (10 ops/s) by default, and can upgrade to 10,000 per 100 seconds (100 ops/s)

The administrative operations consist of Get, List, Create, Delete, ModifyPushConfig, SetIamPolicy, GetIamPolicy, TestIamPermissions. However publishing the message does not count as admin ops (I haven't try subscribing, but looks like it doesn't count as admin ops as well).

In my case every time before sending a message, I was checking if the topic exists or not, and try to create one if it doesn't. By removing that line, the error went away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants