I am running FreeBSD 9 and the following happens: 1. I create a job in a queue called "test". 2. I run /usr/local/etc/rc.d/beanstalkd stop 3. I run /usr/local/etc/rc.d/beanstalkd start 4. The job is gone (no worker who could process the task is online)
Now I do the same but change the way I stop beanstalkd: 1. I create a job in a queue called "test". 2. I run killall beanstalkd 3. I run /usr/local/etc/rc.d/beanstalkd start 4. The job is still in the queue and can be processed So for me this is a different behavior. I called the stop script "clean". Why is this different? Thanks for your reply. Am Dienstag, 20. November 2012 22:49:00 UTC+1 schrieb Ben: > > Hi, > > I started beanstalkd using "-b" to have a binlog created. Now I expected > that every job which is not yet finished/deleted will be restored after a > restart of beanstalkd. In fact the jobs will only be recovered if I kill > beanstalkd via "killall beanstalkd" instead of a clean shutdown. > > Is this the expected behavior? Wouldn't it make sense to keep the log in > any case? > > I am running Beanstalkd 1.6. > > Thanks for help. > -- 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/-/_T4CVoKhzLMJ. 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.
