Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrading from backburner (0.4.6) #118

Open
geoffroymontel opened this issue Feb 21, 2016 · 2 comments
Open

upgrading from backburner (0.4.6) #118

geoffroymontel opened this issue Feb 21, 2016 · 2 comments

Comments

@geoffroymontel
Copy link

Hello

I'm using backburner through Rails Active Job
I tried upgrading from Backburner 0.4.6 to Backburner 1.3 and now the jobs never start now
I'm using backburner:threads_on_fork:work with several queues

Is there an upgrade procedure ?

Best

Geoffroy

@nesquena
Copy link
Owner

Hi Geoffroy,

I would encourage you to stick with 0.4.6 at this time. Unfortunately major changes occurred in the point release which can make the jobs unable to be processed easily and beanstalkd does not make it particularly easy (by design) to iterate and modify existing jobs. You are probably better off sticking with the version that works for you. Sorry I don't have a better answer and sorry for the inconvenience.

@geoffroymontel
Copy link
Author

Hello Nathan

Thanks for your quick reply. Backburner 0.4.6 works kinda well except when the database or the beanstalkd server are restarted. In that case, the workers don't recover the connections. I saw in the changelog that things were improved in that matter in the 1.X releases, that's why I wanted to upgrade.

I will keep an eye on the next releases and restart the rails and workers daily in the meantime.

Best

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants