Hi, I've got a similar issue: lots of DeadlineExceeded errors since a few weeks. I'm on the master-slave datastore too, but what I'm reporting happened again one hour ago.
These errors happen in bursts, and I recently realized that it was in fact shutting down ALL instances of the application. (In the logs, I also have this warning: A serious 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. If you see this message frequently, you may be throwing exceptions during the initialization of your application. (Error code 104)) This does not happen when an instance is spinning up but after several hours. The trace I get along with the DeadlineExceeded errors show that it happens in the second phase: while the app is trying to fallback gracefully because of an other error (that does not appears in logs). Request reported processing time can be like this: ms=100878 cpu_ms=385 api_cpu_ms=58 cpm_usd=0.010945 pending_ms=9321 Here is a screenshot of the admin page, showing that all instances have been shut down about 7 minutes ago, even resident ones: http://dl.dropbox.com/u/497622/spinDown.png The app do work in batches (although not always small ones). But request processing time is usually good enough (see average latency on the screen shot). I'm trying things on my testing applications to see what can be wrong but it's still not clear for me and I'm running short of ideas... Any suggestions? On 2 août, 06:21, Robert Kluin <robert.kl...@gmail.com> wrote: > Hi Will, > I assume this is on the master-slave datastore? I think there were > a number of large latency spikes in both the datastore and serving > last week. > > Some things to try: > - do work in smaller batches. > - if you're doing work serially, do it in batches. > - use async interfaces to do work in batches, but in parallel using async. > > http://code.google.com/appengine/docs/python/datastore/async.html > > Robert > > > > > > > > On Fri, Jul 29, 2011 at 18:35, Will Reiher <wrele...@gmail.com> wrote: > > I'm trying to debug this issue but I keep hitting a wall. > > I keep trying new things on one of my deployments to see if I an get the > > number of errors down but nothing seems to help. It all started in the last > > week or so ago. I also have some existing deployments that I have not > > changed and are seeing these same errors while the code was never changed > > and had been stable. > > 1. This is is happening on existing code that has not changed recently > > 2. The DeadlineExceededErrors are coming up randomly and at different points > > in the code. > > 3. Latency is pretty high and app engine seems to be spawning a lot of new > > instances beyond my 3 included ones. > > > -- > > 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/-/g_C4iPzPeo4J. > > 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.
