-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
Question - Scaling/ Adding more nodes #502
Comments
Yes, at the moment PostgreSQL node scaling is implemented, but not for DCS. I recommend deploying one ETCD cluster of 3 or 5 nodes on separate servers and using it with many Postgresql clusters. |
At the moment my application has to be deployed on 3 physical nodes so having postgres and etcd on same nodes is ideal. What would be the ideal recovery steps should 1 node physically fail? Also if I were to add node separately would I create a new empty linux node then add etc then run add_pg_node and add_balancer node? |
That's right, Playbooks https://etcd.io/docs/v3.5/op-guide/runtime-configuration/#replace-a-failed-machine I understand that managing an etcd cluster manually is not very convenient, so I plan to automate the scaling process for etcd and consul - #503 |
Hey, did you implement scaling? |
Postgres cluster scaling was implemented several releases ago. DCS cluster scaling is planned #503 |
First thank you for this wonderful code!
While going through my testing here in the lab, I stumbled on a potential issue for me.
I deployed a 3 node TYPE A cluster with HAproxy LB and etcd DCS.
In the scaling section you talk about adding a PG node and a load balancer node and you mention that those roles do not scale ETCD or consul.
How would I go about adding 2 more nodes, post initial 3 node deployment?
My use case:
Is this possible?
The text was updated successfully, but these errors were encountered: