Would it be possible to have your consumer remote control a different server to 
process the job and remotely issue the reboot command?  Then polling the remote 
server to see when it comes back up?  In other words the consumer wouldn't 
actually do the work or reboot but would be responsible for telling a 3rd party 
server what to do?   

This way you wouldn't lose the reference to the reserved job, however it would 
add some complexity and additional components to your process.  

-- 
Chad Kouse


On Monday, September 3, 2012 at 12:36 AM, Ben Nagy wrote:

> On Sunday, September 2, 2012 11:31:47 PM UTC+5:45, jab_doa wrote:
> > Hi,
> > 
> > we had the same problem. Basically what we needed is a behaviour like this:
> > * worker reserves job -> job gets reserved
> > * worker dies -> job gets buried
> > 
> > This would be handy for a lot of jobs where the error should get reviewed. 
> > In other cases its ok to just release the job and run it again.
> 
>  Hi Jan,
> 
> This is not the same problem at all. I'm not concerned with a worker dying 
> unexpectedly. I have a pattern where a worker MUST reboot in order to 
> successfully complete the work unit. Once the reboot is done, the worker 
> finishes work, and now wants to delete the job as successfully completed. If 
> anything goes wrong along the way I still want the TTR to kick in and the job 
> to get released.
> 
> Cheers,
> 
> ben 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "beanstalk-talk" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/beanstalk-talk/-/90p17QWXPnUJ.
> 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.

Reply via email to