-
-
Notifications
You must be signed in to change notification settings - Fork 27
Process scale out and coordination #333
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
Process scale out and coordination #333
Conversation
fork master
Feature/python3 support
Feature/coordination redis
…iers in an active active configuration.
Feature/service scale out
|
@nmaludy it wouldn't let me assign you as a reviewer for some reason but this should be good to go. |
…> bytes_to_string created a defined resource to cut down on the copy paste with the scaled services
This should be fixed! |
|
@nmaludy I believe I made all the requested changes |
nmaludy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General comment. Adding redis and the scale out is cool. Would be even better if you could add something to the README so others knew how to configure it.
Thanks, super close!
…ges to the readme
…vice-scale-out Process scale out and coordination
Added Redis install as a coordination backend as even the one liner script installs and the redis package is already included with the base st2 python virtual env (https://docs.stackstorm.com/coordination.html).
Added ability to scale out workflowengine, scheduler, rulesengine, and notifier processes so that they run in an active-active configuration and share the workload. This is important if you want to use more beefy servers to be able to actually use all the resources available (https://docs.stackstorm.com/reference/ha.html#st2rulesengine).
This module was successfully tested on:
RHEL 8
RHEL 7
Ubuntu 16