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

Use proper process manager for backend background services #98

Open
RealOrangeOne opened this issue Jun 5, 2023 · 4 comments
Open

Use proper process manager for backend background services #98

RealOrangeOne opened this issue Jun 5, 2023 · 4 comments

Comments

@RealOrangeOne
Copy link

Running RQ as an unsupervised background process is dangerous, as there's nothing monitoring its availability.

Instead, it should either run as a separate container, or use a proper process manager like s6 inside the container to watch both processes.

@sickelap
Copy link
Contributor

sickelap commented Jun 5, 2023

We are considering Django Q2 to replace Redis RQ. With that, we would be able to use other backend DBs in different scenarios.

@RealOrangeOne
Copy link
Author

That won't fix the issue. The problem isn't needing a separate Redis instance. The problem is running rq_worker in a child process and not monitoring it.

@sickelap
Copy link
Contributor

sickelap commented Jun 5, 2023

I see what you mean. Yea, switching the engine won't solve the issue you are describing. There are other "services" that are spawned within the container.
Extracting RQ to another container seems overkill, s6 looks promising, though.

@RealOrangeOne
Copy link
Author

Ah, I'd missed those - those should probably be moved to process manager.

@RealOrangeOne RealOrangeOne changed the title RQ worker shouldn't run as a background process Use proper process manager for backend background services Jun 5, 2023
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