Any idea how you would handle requests staying in pending for 24 minutes? This happened to me today: https://www.evernote.com/shard/s8/sh/ad3b58bf-9338-4cf7-aa35-a255d96aebbc/4b90815ba1c8cd2080b157a54d714ae0
This server gets about 7 to 12 request per second and usually handles them in ~200ms. But the pending_ms ate all my quota instantly by creating many instances doing nothing but waiting. How should I handle this type of situations? On Friday, October 26, 2012 9:41:31 PM UTC-2, Joshua Smith wrote: > > The only way you could have done that this time is by re-directing your > DNS to someplace completely non-google. > > > On Oct 26, 2012, at 6:18 PM, Benjamin Possolo > <[email protected]<javascript:>> > wrote: > > Hey all. Like most everyone else here. My application was affected by the > GAE downtime this morning. > > I would like to know if there is a good mechanism for detecting this sort > of failure in the future so that my application can automatically throw up > a Maintenance Page. > > Normally I would have an admin section where I can toggle a switch to > render the Maintenance Page but since writing to the datastore was not > working, this isn't really an option. Especially if I can't login to get to > the admin page. > Uploading a new version of my application when a disruption like this > occurs also seems impossible. > > Another idea I thought of was to change my DNS CNAME record to point to a > different server which hosts a maintenance page but the time for the DNS > changes to take effect means this is pretty impractical as well. > > Does anyone have any good ideas? > > I was wondering if anyone using the Capabilities API would be able to > chime in on what their app was seeing during the disruption. > If the Capabilities API correctly identified the GAE state as something > other than "Enabled", then I could see this being a good solution for > automatically redirecting all requests. > > Then again....it seems the problem was that requests were not even > reaching the application servers (due to failed load balancers)....so I > guess that wouldn't have been a solution to the problem this morning > either.... > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/qvOaGAiQXcMJ. > To post to this group, send email to [email protected]<javascript:> > . > To unsubscribe from this group, send email to > [email protected] <javascript:>. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/kCgCaG10Pd8J. 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.
