I've decided to take the approach to wait for the expected number of nodes
to become available before initializing the collection. Here is the script
I am using:
https://github.com/apache/incubator-sdap-nexus/blob/91b15ce0b123d652eaa1f5eb589a835ae3e77ceb/docker/solr/cloud-init/create-collection.py
First, for a given data set, I can easily double or halve
the size of the index on disk depending on what options
I choose for my fields; things like how many times I may
need to copy fields to support various use-cases,
whether I need to store the input for some, all or no
fields, whether I enable
Thanks, I am no Solr expert so I may be over-simplifying things a bit in my
ignorance.
"No. The replicas are in a "down" state the Solr instances are brought back
up" Why can't I dictate (at least initially) the "up" state somehow? It
seems Solr keeps track of where replicas were deployed so that
bq. do all 100 replicas move to the one remaining node?
No. The replicas are in a "down" state the Solr instances
are brought back up (I'm skipping autoscaling here, but
even that wouldn't move all the replicas to the one remaining
node).
bq. what the collection *should* look like based on the
Thanks for the response. You do raise good points.
Say I reverse your example and I have a 10 node cluster with a 10-shard
collection and a replication factor of 10. Now I kill 9 of my nodes, do all
100 replicas move to the one remaining node? I believe the answer is, well
that depends on the conf
How would you envision that working? When would the
replicas actually be created and under what heuristics?
Imagine this is possible, and there are a bunch of
placeholders in ZK for a 10-shard, collection with
a replication factor of 10 (100 replicas all told). Now
I bring up a single Solr instanc
Hello,
I am trying to bootstrap a SolrCloud installation and I ran into an issue
that seems rather odd. I see it is possible to bootstrap a configuration
set from an existing SOLR_HOME using
./server/scripts/cloud-scripts/zkcli.sh -zkhost ${ZK_HOST} -cmd bootstrap
-solrhome ${SOLR_HOME}
but this
