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:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB