Thanks, that was the response I was expecting unfortunately.
We have to stop the cluster to add a node, because Solr is part of a larger
system and we don’t support either partial shutdown, or dynamic addition within
the larger system.
“it waits for some time to see other nodes but if it finds
And to pile on Shalin's comments, there is absolutely no reason
to try to pre-configure the replica on the new node, and quite
a bit of downside as you are finding. Just add the new node
without any cores and use the ADDREPLICA command to cause
create replicas.
Best,
Erick
On Thu, Jun 4, 2015 at
Why do you stop the cluster while adding a node? This is the reason why
this is happening. When the first node of a solr cluster starts up, it
waits for some time to see other nodes but if it finds none then it goes
ahead and becomes the leader. If other nodes were up and running then peer
sync and
Hi,
I am seeing some unexpected behavior when adding a new machine to my cluster. I
am running 4.10.3.
My setup has multiple collections, each collection has a single shard. I am
using core auto discovery on the hosts (my deployment mechanism ensures that
the directory structure is created and
