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

Deploy Highly Available OpsCenter Nodes #30

Closed
mahthi opened this issue Jul 12, 2015 · 5 comments
Closed

Deploy Highly Available OpsCenter Nodes #30

mahthi opened this issue Jul 12, 2015 · 5 comments

Comments

@mahthi
Copy link
Contributor

mahthi commented Jul 12, 2015

Today, we deploy one opscenter node is susceptible to downtimes. Is it possible to deploy 2 nodes and use the second one for failover?

@benofben
Copy link
Contributor

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.

@mahthi
Copy link
Contributor Author

mahthi commented Jul 24, 2015

Is it okay if OpsCenter is down from time to time for more than 30 minutes?

@stinkymatt
Copy link
Contributor

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.

@benofben benofben changed the title Deploy OpsCenter Nodes in a Highly Available fashion Deploy Highly Available OpsCenter Nodes Aug 6, 2015
@benofben benofben reopened this Aug 6, 2015
@benofben benofben self-assigned this Sep 14, 2015
@benofben
Copy link
Contributor

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

@benofben
Copy link
Contributor

benofben commented Feb 7, 2016

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.

@benofben benofben closed this as completed Feb 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants