On Tue, Jan 19, 2010 at 5:41 AM, Ahmad Amireh <[email protected]> wrote:
> I'm attempting to create a web front-end for 'managing' our beanstalkd
> server, and by managing I mean the ability to:
>  * browse watched and used tubes
>  * browse jobs belonging to a certain tube {ready | buried | delayed}
>  * bury a job, delete it, or modify its priority
>  * view currently active / reserved jobs
>
> ...
>
> I'm really confused because it's looking to me like it's alot of
> trouble to retrieve this data or manage jobs. How do you guys do it?
> And am I way off with what i'm trying to accomplish?

So far I haven't seen a lot of interest in doing these sorts of
things, but maybe that is just because the self-selected set of people
who post on this list or talk to me haven't been turned off by these
shortcomings. I can certainly understand the desire to have more
visibility into the queue and control over the jobs.

I see no fundamental reason why the bury command shouldn't work on
ready jobs, or why you should not be able to change a ready job's
priority.

However, I don't know how useful these things will be in a production
system, unless it's very lightly loaded. Beanstalkd is designed to
process many millions of jobs per day. At that rate, a tool that
reserves an entire tube to list out the jobs will become a bottleneck.
Similarly, you might not get the chance to bury or re-prioritize jobs
because they will fly by too fast.

That said, I'd certainly accept patches to do these things. And I'm
still thinking about a way to iterate over the contents of a tube.
There was a discussion about that a while back, but so far I haven't
seen or thought of any good solutions. If anybody has further thoughts
on that, I'm all ears.

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