Status Update
No update yet.
Comments
va...@google.com
du...@google.com
Hello,
Thank you for contacting the Google Cloud support team.
I have gone through your reported issue, however it seems like this is an issue observed specifically at your end. It would need more specific debugging and analysis. To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system. I'm going to close this issue which will no longer be monitored. If you have any additional issues or concerns, please don’t hesitate to create a new issue on the
We appreciate your cooperation. Thank you!
Description
Over the last few days, some of the requests on multiple services started failing which appears random behavior. Also, when investigated, they all seem to have similar reason as "Process terminated because of the max instances setting." But in all cases, there was room to scale up.
For example in one such scenario:
Error reported: The request was aborted because there was no available instance. Try increasing the max_instances value in your app.yaml. More information at:
No parallel requests on the version of the service.
Autoscaling config:
min_instances: 0
min_idle_instances:0
max_instances: 1
Instance class: F1 (384 MB)
Last memory peak (30 mins before the actual request on the error) - 203 MB (approx.)
Memory was available, there was no traffic on the service except the mentioned request.
Please suggest a solution to this problem.