Yeah inspecting data currently on the tube would be great. We
currently fake this by iterating through the whole tube and putting
jobs back at lower priority. It isn't clean or nice, but we have to be
able to go through tubes and removed jobs that were created in a error
or problematic case. Occasionally we have a problem that creates
thousands of bad jobs, and we don't want to loose other peoples good
jobs just by emptying the whole queue.

I think you are correct that most of their feature requests do come
down to that single request.

peace,
Dan Mayer
Co-founder, Devver.net (http://devver.net)
http://twitter.com/devver
http://mayerdan.com
http://twitter.com/danmayer



On Tue, Nov 3, 2009 at 4:52 PM, Keith Rarick <[email protected]> wrote:
>
> On Tue, Nov 3, 2009 at 10:28 AM, Dustin <[email protected]> wrote:
>>  Github did a post on their queuing system (including things they
>> didn't like when they ran beanstalkd).  Useful info:
>>
>>  http://github.com/blog/542-introducing-resque
>
> Thanks, that is useful. I should probably treat that as a set of
> feature requests (many of which are new).
>
> Actually, now that I think about it, all of their beanstalkd "missed
> DJ features" boil down to one thing: inspecting or paging through the
> entire contents of a tube. Everything else is best done in terms of
> that.
>
> "Seeing failed jobs." Most normal people use logging for this, but if
> you really want to put it into the queueing system, you just make a
> "failed" tube and stick data in it. Then page through that tube.
>
> "Seeing pending jobs." Page through the tube.
>
> "Manipulating the queue." Page through the tube you need to edit and
> delete or resubmit various jobs. As always, beanstalkd is dumb; you do
> all the decision making in the client. (You can fake this by reserving
> jobs and copying them to another tube, making your edits along the
> way. We did this all the time at causes. But it's not optimal.)
>
> So, it's not obvious how to do paging in a reasonable way in
> beanstalkd, but maybe it deserves some thought.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to