On Jan 9, 2010, at 0:00, Keith Rarick <[email protected]> wrote:
On Fri, Jan 8, 2010 at 8:56 AM, Graham Barr <[email protected]> wrote:
I would like to suggest two new reserve commands
reserve-limit LIMIT
reserve-limit-timeout LIMIT TIMEOUT
I understand your use case, but I'm reluctant to add more options to
the reserve command. Next time we'll wind up with 8 reserve commands,
then 16... :)
That could be mitigated by making this an option for the watch
command instead:
watch-limit <tube> <limit>
Hm, ok. I will have to think about that a little more as it will mean
storing that within the conn struct and making that available when
reserving
I was thinking about adding to tube-stats a time value as how long
ago
last worker activity happened (ie reserve, delete etc)
That sounds good to me. There is also the current-watching tube stat.
Not sure if that's good enough.
current-watching does nou help as it is not a sign of activity. If a
worker gets stuck it is still counted as watching.
Graham
kr
--
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
.
--
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.
