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
Autoscaling resque question #1896
Comments
Does the master process require it be running monolith style to control all the workers across various nodes? Is there a way to configure this (not kubernetes) or is it all just going to be ok, spinning this thing up over and over again, with various master processes that are only aware of their own nodes? is any state contained within the resque master process or does it keep everything that other resque containers might need to know in redis just by default? |
The way I have been running it in production at scale is to have a decoupled redis database living outside of the k8s cluster and then just let the autoscaler do its thing depending on workloads. Usually I work off CPU or Memory depending on the system, but there are also ways to autoscale based on number of jobs in a queue for example. The way I structure the setup is like this:
Hope that answers your questions! |
Can I safely autoscale a rails container running resque...? It'd be connecting to a shared / decoupled database and redis instance.
I have a concern that when multiple resque/rails containers are running, that the queues might get weird? would each resque container need its own redis instance to talk to, or can they all just talk to the same redis?
The text was updated successfully, but these errors were encountered: