Can someone from the AppEngine team help us understand whether these issues are related to recent data store problems?
In theory, I don't think they should be, because at least for me I'm seeing DeadlineExceeded very early on -- somewhere in Django before any of my code is run. But that's theory... I was hoping for a comment on practice. ;-) Cheers, Dave On Jun 2, 2:19 pm, scarlac <[email protected]> wrote: > +1 > We've been having way too many of these errors for two weeks. Downtime > is acceptable but this is ridiculous. This can't keep up or we'll have > to rewrite our app and stop using appengine. We choose Google and > expected stability and scalability so I'm very disappointed at the > moment. > > On Jun 2, 12:16 am, Dave Peck <[email protected]> wrote: > > > > > Hi, > > > In the past week, I've seen an alarming number of DeadlineExceeded > > exceptions on cold hits to my applications. > > > Most of the stack traces are shallow -- things blow up well before my > > code is hit. Seehttp://pastie.org/988269fora stack trace. > > > The `bootstrap.py` file is more-or-less a direct copy of the `main.py` > > from Rietveld. > > > Can someone on the App Engine team please point me in the right > > direction here? This is a big change in GAE's behavior in the past > > week, and it is affecting many of my applications (citygoround which > > has been in production for half a year; code-doctor which is under > > development, etc.) > > > Cheers, > > Dave Peck -- 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.
