After some hacking... Backends work like normal always.
A trick to resolve frontend instances is temporarily to set the number of resident instances to a static number like Idle Instances: ( 3 – 3 ) This seems to fix the issue (essentially disabling the scheduler) but is undesirable for many reasons. I'd love to hear Google's opinion on the matter. On Friday, December 6, 2013 6:23:00 PM UTC-5, Christopher Ritter wrote: > > We've been down for the last few hours (app id: gfmcommonview). > > The lack of any official Google response is frustrating. > > We're a long time customer of GAE with many apps deployed but these errors > and the non-existent responses from Google when problems like this occur > make me start to question the future of the platform. > > On Friday, December 6, 2013 5:58:48 PM UTC-5, Rik wrote: >> >> I haven't seen one for over 24 hours at this point. >> >> On Thursday, December 5, 2013 2:17:17 PM UTC-8, Rik wrote: >>> >>> Getting a lot of 500s with this error: >>> >>> A problem was encountered with the process that handled this request, >>>> causing it to exit. This is likely to cause a new process to be used for >>>> the next request to your application. (Error code 121) >>>> >>> >>> Anyone else? >>> >> -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
