Assigned
Status Update
No update yet.
Comments
su...@google.com
I also experience a high number of 502 in europe-west1
ju...@uptimal.com
We suspect that we may be running into some sort of rate limit. The Cloud Tasks API Quota for maximum requests per minute is rather high (6 million/min) and we're not even close to that, but we believe that when we have bursts of task creation that the API then throws the 502.
su...@google.com
Any update on this? It seems to be happening again. We are experiencing both high latency and 502, the requests are seconds apart.
ga...@google.com
Thanks for raising this issue.
I have forwarded this as a feature request to the product management team. Note that there are no ETAs or guarantees of implementation for feature requests, but you can track this thread to post any further comments or check the updates regarding this.
Best regards
ju...@uptimal.com
Thanks,
Sure, no need for ETA or guarantees - I just thought it would be a nice to have,
Best,
Sure, no need for ETA or guarantees - I just thought it would be a nice to have,
Best,
Description
Cloud Tasks is sharing Global Scope among tasks of the same queue (not sure if even shares it with other queues) while using Cloud Run to run the handler and Node.js runtime. Could be that this is the expected behaviour for reasons that I don't get to see but nevertheless it is dangerous as I think it is unexpected for most of the developers.
Could it be possible for the global scope of each task to be completely independent?
Thanks,