OK, I managed to catch one. I saved the appstats page, as well as the logs, here: https://dl.dropboxusercontent.com/u/4066735/LiteRumble_error/LiteRumble_error.zip If you want to step through code the latest is available here: https://bitbucket.org/jkflying/literumble/src/3542f1e636fe8675cf6e5b70126d271963386e71/BatchRankings.py?at=default
In the appstats, further down I'm seeing memcache.Set() entries with times such as "real=8831941ms", which is clearly where it is hanging. Personally, I don't consider 8000 seconds, that is over 2 hours, reasonable latency in a single memcache Set() call ;-) Also, this handler only terminated because I did a manual shutdown of the instance. In the log I linked you see the /_ah/stop being called just before the memcache.set 'woke up' after being hung for 2 hours. Thanks for the help Julian On Saturday, 24 August 2013 05:05:33 UTC+2, Vinny P wrote: > > On Fri, Aug 23, 2013 at 1:36 AM, Julian Kent wrote: > >> Will do. Right now it is tough to catch these though, they only happen >> ~20% of the time. It always seems to happen while I'm asleep :-/ Is there >> some way of getting appstats to save to db so I can see it later? >> > > > 20% occurrence rate is more than enough for appstats to retain the > appropriate data. We don't need to see every single failure, just a few > good examples of what the memcache calls are doing and how long they take. > > > ----------------- > -Vinny P > Technology & Media Advisor > Chicago, IL > > App Engine Code Samples: http://www.learntogoogleit.com > > -- 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.
