I second that. In many situations, we need to expose a global status of the queues, with opportunity for an administrator to take action on some failed jobs, or queued jobs.
Of course, beanstalk is a queue manager at first, and should not be seen as an array of jobs. In my case, I'm managing process-intensive jobs that require a human to take action based on a complex technical context. Ideally, I'd need to get simple lists of JOB ids. Real job data is stored in a database-table. What I really need is a simple list of job-id's in a "ready" state, currently reserved or buried. Today, I have to reserver-all then release-all to simulate this behavior. I have no idea of what jobs are being processed. Thanks! On Apr 3, 12:13 pm, Jurian Sluiman <[email protected]> wrote: > Hi Keith, > > On Apr 3, 10:39 am, Keith Rarick <[email protected]> wrote: > > > If you're not concerned with performance, you can > > reserve all the jobs in the tube, then release > > them all again. This will give you a chance to > > inspect the entire contents. > > > kr > > This is a valid option if you want to have a list of all ready jobs. > Because I want to give users the chance to kick or delete buried (i.e. > failed, in my case) jobs, is there an option to "reserve" failed jobs > without kicking them? If I kick them, they will interfere with other > normal jobs, which should be passed through to the normal workers. > > -- > Jurian Sluiman -- 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.
