When an instance returns to many sequential 5xx errors, our instance scheduling system will consider the instance unhealthy. The instance scheduler will then terminate this instance.
When an instance gets terminated, and it still has a request queued, the queued request will throw the 203 error. While the instance is being terminated, no new requests get queued for that instance by our scheduler. This means that the 203 only gets thrown when there's a request queued when the instance gets terminated, and only for the request that was queued. The root cause is should in fact be that our instance scheduler will terminate an instance that serves to many sequential 5xx errors, and this is expected and desired behavior. The cause of the problem that needs to be addressed is this high incidence of 5xx errors. You could filter the logs by the instance Id and look at the 5xx errors prior to the instance shutdown to verify this claim. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1be25cf1-6361-4a48-ac97-d4a4061c50b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
