Scaling - How to handle updates to node configuration while scaling up a cluster

[proddata]

Pitch

Documentation feedback

• Page title: CrateDB multi-node setup
• Page URL: https://crate.io/docs/crate/howtos/en/latest/scaling/multi-node-setup.html
• Source: https://github.com/crate/crate-howtos/blob/master/docs/scaling/multi-node-setup.rst

---

This issue originated from a question about propagation of settings of newly joined nodes, while scaling up a cluster. ("Let's say I have a 3 node cluster and have thus set gateway.expected_nodes to 3 in the startup commands for those 3 nodes. If I now add 1 additional node and start it with -Cgateway.expected_nodes=4, will the "4" propagate to the existing 3 nodes in some way or do I need to restart the 3 nodes?"). The how-to should include the best practice for the necessary steps (e.g. updating config on all nodes / ? restart?) that need to be performed, when scaling up an existing cluster.

[nomicode]

thanks for the feedback, @proddata!

we have an open work item at the moment for improvements to the scale-up and scale-down documentation. I have added this issue to our list. someone from the @docs team will update you here when we have updates to share :)

[amotl]

Hi @hammerhead,

isn't this (see also #21) also something which could be reflected as another tutorial at [1]?

With kind regards,
Andreas.

[1] https://community.crate.io/c/tutorials/28

[hlcianfagna]

Partially covered in https://community.crate.io/t/how-to-add-new-nodes-to-an-existing-cluster/1546

[amotl]

I've added a patch to cross link to the article you've referenced. Thanks!

• Administration/Clustering: Reference articles about scaling clusters #46