Also, the core name is presumed to be a unique identifier.
So when you say you "cloned" the machine, did you also
clone the entire replica's directory? Ss Scott says, the
core.properties file contains, among other things, the
coreNodeName of which there should be one and only
one per collection. So
Hi Teddie,
Take a look at the core.properties file on the cloned or clone. I suspect
there's info in it that describes which collection and shard that node is
responsible for. Zookeeper maintains a mapping of node addresses to cores
and you can lock a node out of the cluster if you're not careful.
Hi,
I have a SolrCloud cluster with 3 nodes running on AWS. My collection is
created with numShard=1and replicationFactor=3. Recently, due to the need of
having stress test, our ops cloned a new machine with exactly the same
configuration as one of the nodes in existed cluster (let's say the new
m
Hi,
I have a SolrCloud cluster with 3 nodes running on AWS. My collection is
created with numShard=1and replicationFactor=3. Recently, due to the need of
having stress test, our ops cloned a new machine with exactly the same
configuration as one of the nodes in existed cluster (let's say the new
m
