Hello all, I'm trying to make heads-or-tails of this. Lately I've seen a few worrying requests where, on a cold start, memcache fails and the resulting enormous stacktrace wipes out the history in my logs, so the charts end up empty.
A cold start request such as this one will typically make about 10 contains() and get() requests on the memcache. I don't understand why the request didn't error out, or how it produced such a gigantic trace. Here it is, in all its beauty: http://dl.dropbox.com/u/353497/gae.txt Please forgive the crude removal of internal details from that file. The occassional memcache failure isn't a big deal, its the monster stacktrace that I'd like to avoid. Any insight into how this happens would be much appreciated. Also, after a couple of weeks of absolutely stellar performance from GAE following March's rough patch, my app is back to rapidly-cycling instances getting killed and spun up. Anyone else seeing anything similar? Appid: hrkleio Thanks! -- 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.
