Hi Vlad, Wanted to let you know I starred this issue.
You had suggested, I think, this I set this issue up given my rants about the lack of real-world concern re: taskqueue features. (I.e. GAE cannot reliably handle Paypal ExpressCheckout.) Afraid that my world-wearly cynicism about GAE engineers being concerned kept me from doing this. Hopefully I'm wrong and this will get immediate attention -- likely though we'll get the new API from Guido first. (Oops, there's that WWC.) Cheers, Steve On Apr 18, 4:22 pm, vlad <[email protected]> wrote: > GAE folks actually answered this question some months back. What they said > is backoff specified in queue.yaml only a cue for the scheduler. Scheduler > does not come back to check the queue to see if retries are needed UNLESS it > needs to do that anyway. If there are other tasks pending to be fired > between moment your task failed and time specified in your backoff schedule > , then you MAY see backoffs to behave closer to what you specified in > queue.yaml > In other words, IF you happen to run a lot of tasks then your average > behavior will be better than an isolated test case you are focusing on. > > This is very frustrating. I would be happy to pay more CPU cost to make > TaskQueue behave more predictably. > Starhttp://code.google.com/p/googleappengine/issues/detail?id=4901if you want > that too. > > Bottom line: You can workaround this problem by firing a dummy task on the > same queue every second. > > Btw, i think you are right assuming GAE folks are not terribly proud of > this design :) -- 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.
