Nick,
Thanks much! i started leasing tasks again and it appears to be working.
I've been through a few thousand tasks, only 19 million more tasks to go!
thanks for keeping me updated.
christian
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engi
Christian,
The presumed fix was pushed out to production a few hours ago. If you
want to try leasing from your eventpull queue again, you should have a
better rate of success.
Nick Verne
On Tue, Feb 28, 2012 at 10:45 AM, Christian Foster Howes
wrote:
> thank you!
>
> i'll stop writing to it as
thank you!
i'll stop writing to it as soon as i can get the change in my code. :)
please let me know if you need help from me to debug or test.
christian
On 2/27/12 15:43 , Nicholas Verne wrote:
If the queue is deadlocked in the way I suspect, it will remain so
regardless of whether your app
If the queue is deadlocked in the way I suspect, it will remain so
regardless of whether your app accesses it from a backend or frontend
instance.
I'll respond in this thread.
Nick Verne
On Tue, Feb 28, 2012 at 10:28 AM, Christian Foster Howes
wrote:
> Nick,
>
> thanks for the info! 2 follow-o
Nick,
thanks for the info! 2 follow-on questions:
- do you expect that i can read the queue from a front-end instance?
- where do i sign-up to be notified that a fix is in place? (is there
a bug number i can follow?)
thanks so much for the help, and the great product!
christian
On 2/27/1
Christian,
Your problem sounds like an instance of a rare condition in our
backends that can cause deadlock in a pull queue. We are working on a
fix that should be pushed out in the next few days. If you're prepared
to wait a couple more days, you may be able to consume your remaining
tasks withou
Hello,
I have a pull queue that i have been getting:
File
"/base/python_runtime/python_lib/versions/1/google/appengine/api/taskqueue/taskqueue.py",
line 1423, in lease_tasks
raise self.__TranslateError(e.application_error, e.error_detail)
TransientError
for the past day. to put it in p
