WAI
Status Update
Comments
[Deleted User] <[Deleted User]> #2
Could this be the cause? https://cloud.google.com/run/quotas
32M response limit. Can I get that increased, please?
32M response limit. Can I get that increased, please?
si...@google.com <si...@google.com> #3
Thanks for reaching out with this issue. Let me also thank you for providing a reproducible example via the Github repository. That was very helpful with the replication of the issue.
As for your conclusion that this might have been caused due to the deployment hitting the Response-limit quota, you’re most likely correct. In my replication, upon sending a curl command with size=31 and another one with size=33, the size=31 completed successfully whereas the size=33 failed with Error 500.
As for the requested for a quota increase, I regret to inform that we cannot increase it at the moment, as can be seen in the official documentation [1]. The only Cloud Run quota that can be increased is the maximum number of container instances per service.
Since this is working as documented and expected, I’ll move forward to close this issue. If other issues arise in the future, feel free to contact us.
[1]https://cloud.google.com/run/quotas#cloud_run_limits
As for your conclusion that this might have been caused due to the deployment hitting the Response-limit quota, you’re most likely correct. In my replication, upon sending a curl command with size=31 and another one with size=33, the size=31 completed successfully whereas the size=33 failed with Error 500.
As for the requested for a quota increase, I regret to inform that we cannot increase it at the moment, as can be seen in the official documentation [1]. The only Cloud Run quota that can be increased is the maximum number of container instances per service.
Since this is working as documented and expected, I’ll move forward to close this issue. If other issues arise in the future, feel free to contact us.
[1]
an...@gmail.com <an...@gmail.com> #4
Understandable.
But, can we please return something other than "500 Internal Server Error"? It was very confusing.
May I suggest:
501: Response limit reached. Seehttps://cloud.google.com/run/quotas for details.
But, can we please return something other than "500 Internal Server Error"? It was very confusing.
May I suggest:
501: Response limit reached. See
Description
Problem you have encountered:
Our image-scaling service fails on large files, such as piping videos from a storage-bucket. There is no error reported by the Go program, it just hangs after calling io.Copy. Then the cloud-run loadbalancer answers the browser with 500.
What you expected to happen:
I expected it work like it does locally, or in a local Docker container. Where it pipes the files from the bucket without issues.
Steps to reproduce:
I created a little project to reproduce this with as little code as possible.
Other information (workarounds you have tried, documentation consulted, etc):
Ruled out:
This service simply writes 'A' bytes to the size requested. Works for 1M 10M, but not 50M 100M, etc.
There is also a thread on Stackoverflow: