> Quick poll: Should we remove even that restriction, simply allowing > delete and bury to operate on absolutely any job?
I was wanting this kind of behavior a while ago. That is, I wanted to be able to operate on an arbitrary job given its job id. I think this could come in handy. /Cody On Tue, Feb 2, 2010 at 1:52 PM, Keith Rarick <[email protected]> wrote: > On Mon, Feb 1, 2010 at 4:39 AM, sebest <[email protected]> wrote: >> Hello, >> i noticed that few of my jobs have a strange value for their time- >> left, so they don't get rescheduled. > > What TTR value did you supply in the `put` command for those jobs? The > client is allowed to specify an extremely large TTR. > > I don't rule out the possibility of a beanstalkd bug, but the client > could just as well be responsible. > >> By the way, is there anything i can do with a job in the reserved >> state? it seems i can't delete or release it even if i know it's jid. >> >> I currently have 5 jobs in this strange status, is there anyway to >> delete them, or list them? > > Those jobs are currently being processed by workers. Only the worker > running a reserved job is allowed to modify that job (release or > delete or bury). Also, if you kill the worker, beanstalkd will release > the job. > > Quick poll: Should we remove even that restriction, simply allowing > delete and bury to operate on absolutely any job? > > 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. > > -- 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.
