Update on our case. After a bunch of refactoring and improved cache usage, our quotas seem to be back to normal as of yesterday. But I'm not 100% convinced the optimizations were enough to cut the quotas in half (but I'm sure it helped). I re-checked the taskqueue angle, but just couldn't find any issues there.
I hope you get a reply from Google as to what exactly happened here, and please do keep us posted. On Tuesday, November 25, 2014 1:11:01 PM UTC+8, Kaan Soral wrote: > > That's great to hear, thanks a lot for the reply > > The other thread I linked is from another app of mine, it doesn't have > extreme traffic so I was able to inspect the error logs, although they were > from 2 days ago, the issue might have persisted 2 days (they ended 2 days > ago for that app) > It was a simple import error causing the tasks (deferred etc) to retry for > that app > > I'm guessing the same issue caused the initial triggerer tasks to retry > for my app, causing the clogging and the extreme aftermath, I might even > lose everything with the percussions of the issue > > TL;DR; You might not have seen the clog, if your taskqueues were broad > enough to handle the extra capacity, the tasks might have just > repeated/completed and you've probably observed the issue only from the > increased costs > -- 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/d/optout.
