Well, first of all you need to bootstrap a system - so all the nodes should know of each other. This hasn't changed in 3.5. When you add a new server, you also need to bootstrap its config file with something (there are a few suggestions in the manual) - it doesn't need to be the latest config but it has to include the leader and it must be specified in a way that avoids a split brain. Once the new server talks with the leader, it syncs the latest configuration (something like what you're saying). Then you can issue a command to formally add it to the cluster.
On Fri, Jul 14, 2017 at 2:09 PM, Luigi Tagliamonte < [email protected]> wrote: > Thank you for the reply > I was thinking that this whole automatic reconfiguration was something like > in Cassandra...you have a seed node and when a new node boots it get the > info from the seed. Is something like that available? > Regards > L. >
