>> Got a few questions as far as looking into what the system is doing.
>> I've used Resque in the past and am in the process of reading up on
>> beanstalk and seeing if it is a viable replacement.
>> 
>> 1. Is it possible to get a list of jobs that are in a tube?
> 
> You can reserve them to look at them and then let them be returned
> (i.e. don't delete the job).

What if there are thousands of jobs in the queue? It doesn't seem right to go 
reserving a thousand jobs just to put them back on the queue.

>> 2. What happens with failed jobs? (this may be client side)
> http://nubyonrails.com/articles/about-this-blog-beanstalk-messaging-queue
> failed in what sense? A client reserves a job. a client does the work.
> the work fails. The client could then delete the job and you handle
> the failure in the program, or you could bury the job so it's in the
> queue but not available until someone specifically pokes it.
> Personally I prefer to handle failures in my applications and delete
> the job since it's unlikely the job is going to succeed if run again.
> If you're going to re-run jobs you also want to make sure that won't
> mess up the system (you may need to back out of transactions/etc based
> on what you are doing). If you're going to rerun jobs you should make
> sure they are idempotent. http://en.wikipedia.org/wiki/Idempotence
> 

In my case I just need a back trace of what went wrong. Resque provides a great 
interface for this, an let's me manually requeue the job.

>> 3. Is it possible to get a list of queues that a worker is watching?
> 
> Yup, you ask the client.

I was hoping to avoid asking the client. Say you have hundreds of workers, 
querying each of them doesn't seem to make much sense since the server already 
knows what queues the worker is watching in order to send it jobs. 

> 
>> 4. Is it possible to get the current job that a worker is working on?
> 
> Well you ask the client and it says "I am working on job id X"

This works, but seems like a lot of overhead for the case of hundreds of 
workers. 

> 
>> Thanks,
>>  - James
> 
> -Kurt
> 
> -- 

- James
> 

-- 
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