I've found three tricks to be helpful: 1. Do not use the default queue unless you have totally debugged your code. The default queue is set so that a runaway task process will max out the quota very quickly.
2. Stick to about one queue per task to have a better idea of what's going on. 3. If possible, give yourself runtime control of task handlers via the datastore. I've used a small global entity with a "stop" attribute. If TaskControl.all().get().stop == True, the handlers would short- circuit out one by one until the queue was empty again. On Aug 17, 12:30 pm, Philippe <[email protected]> wrote: > http://code.google.com/p/googleappengine/issues/list > you can star some issues on taskQueue. it's still in the lab of > appengine team. > > On Aug 17, 12:21 am, Sebastian Aviña <[email protected]> wrote: > > > Hi, I'm running some task queues on my app hola-dgo, right now I have > > exceded the Total Daily Quota, and I still have around 2000+ tasks in > > queue... I don't know which tasks are queue, I can't see them, neither > > I can't delete, or flush the queue... What can I do? > > > It's very hard to debug task queues on the production environment, > > because there is no way to know which tasks are queued... > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
