3

I have encountered this error frequently from Oct/11/2019.

The request was aborted because there was no available instance.

So I deploy to cloud run, I can't access to the service. and always display

>Error: Server Error
>The server encountered an error and could not complete your request.
>Please try again in 30 seconds.

What happened on cloud run instances? Is this correct behavior?

I know this error is posted to troubleshooting . But I have never encountered this error until recently. So I can't understand why I got this error suddenly.

Y Natsume
  • 61
  • 3
  • 1
    Please check this related question [link](https://stackoverflow.com/questions/57007386/how-to-fix-cloudrun-error-the-request-was-aborted-because-there-was-no-availabl/57013896). – marian.vladoi Oct 11 '19 at 13:01
  • 3
    Possible duplicate of [How to fix CloudRun error 'The request was aborted because there was no available instance'](https://stackoverflow.com/questions/57007386/how-to-fix-cloudrun-error-the-request-was-aborted-because-there-was-no-availabl) – Dustin Ingram Oct 11 '19 at 13:08
  • You have not provided enough detail about your use case to provide an answer. We can only provide tips and guesses. For example, is this the only request, did you have a sudden burst of traffic, how long does your container take to start responding (cold starts), etc? Additional information that might help is the log entries from Stackdriver. – John Hanley Oct 11 '19 at 19:38
  • There another case if you set the `max-instances` param too low according with your traffic. – guillaume blaquiere Oct 11 '19 at 20:26
  • yes, i set `max-instances` before I encountered this error. but I set enought instances(=5) and concurrency(=5). cloud run can't serve just 1 request at that time. but now, the error doesn't happend.(maybe it's due to beta test.) – Y Natsume Oct 21 '19 at 04:58

0 Answers0