Using beanstalk 1.3 I find that if I put a job with TTR=5 and reserve it
indefinitely the job will not time out until the client that reserved
the job does something on its socket.
i.e. using 2 telnet sessions:
Session #1:
put 1 0 5 1
b
INSERTED 2
Session #2:
stats-job 2 (repeatedly)
I observe that the 'time-left' falls to 0, then overflows negative
(time-left: 4294967249) but the 'timeouts' stays on 0.
As soon as I return to Session #1 and run a 'stats' or anything then the
'timeouts' increments and the job returns to ready state.
Is this the expected behaviour?
>From the protocol doc I would have expected the TTR to be enforced
regardless of what the client does.
cheers,
yun
--
Yun Huang Yong
[email protected] ...nom nom nom
+61 408 131 419
--
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"beanstalk-talk" 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/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
