-
Notifications
You must be signed in to change notification settings - Fork 44
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
Deploy Highly Available OpsCenter Nodes #30
Comments
We could deploy multiple OpsCenters. I'm not sure building that into the template is desirable as that adds considerable complexity. OpsCenter is not critical for the functionality of a DSE cluster. It is merely a monitoring interface. |
Is it okay if OpsCenter is down from time to time for more than 30 minutes? |
OpsCenter did get an HA config option in 5.1. I would consider this a lower priority than some other things, but it would be nice to have for larger clusters. |
In the new main template I'm putting OpsCenter in its own Vnet/subnet/template functions. With it compartmentalized, it'll be easy to add additional nodes if desired. #42 |
We haven't really been asked for this. OpsCenter redundancy isn't necessary for a cluster to continue operating. If the node does fail, it can be replaced manually. Given all that I'm closing this. |
Today, we deploy one opscenter node is susceptible to downtimes. Is it possible to deploy 2 nodes and use the second one for failover?
The text was updated successfully, but these errors were encountered: