A request handler has a limited amount of time to generate and return a response to a request, typically around 60 seconds. Once the deadline has been reached, the request handler is interrupted So optimise you procedure or if the queryset is too big then use the cursor and memcache functionality.
On Mon, May 7, 2012 at 11:47 PM, someone1 <someo...@gmail.com> wrote: > Starting about 15 minutes ago, my app has logged excessive amounts of > deadline exceeded errors and the website is not loading on most requests. > Please e-mail me privately if you require an appid! Site hasn't had any > issues since launching its current default version a week ago. > > HR data store, threading enabled, py27, 1-2 Idle instances, F1 instances, > automatic - 1.0s pending latency > > Thank you, > Prateek > > -- > 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/-/Hs7GNLogieUJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
