I experienced the same problem for a few minutes on this past Thursday, unfortunately it was during a sales pitch. I wish Google would let us buy our way into a more reliable uptime, some apps need to be up no mater what, while others can tolerate sporadic errors.
On Oct 9, 2:13 pm, Zarko <[email protected]> wrote: > We see elevation in 500 requests ("Request was aborted after waiting > too long to attempt to service your request. This may happen > sporadically when the App Engine serving cluster is under unexpectedly > high or uneven load. If you see this message frequently, please > contact the App Engine team.") > today also... > > On Oct 9, 7:55 pm, John Gardner <[email protected]> wrote: > > > > > After exercising the site a while, it's smoothed out. It seems like > > the 500 errors were from trying to spin up new instances. The site > > was completely idle before visitors arrived and the 500 storm started. > > > It seems like reserved instances is a *critical* feature. There's no > > way we can leave beta when the first impression a user gets of our > > site is a 500 page. We have billing enabled, but all the quota in the > > world doesn't help if the user sees an error page and walks away... > > > -John > > > On Oct 9, 12:30 pm, John Gardner <[email protected]> wrote: > > > > We're getting constant DeadlineExceededErrors on our production site > > > this morning. > > > > Our app ID is cxiongame. I'm unable to log in; the login request runs > > > into the deadline, when this is ordinarily completed in less than 1 > > > second. > > > > -John -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
