: >> 2) a single "extra" solr node in the cluster can be used as a "self : configuring" load balancer : : I’ve thought about this a bunch before, are there mechanisms to instruct : Solr to not host shards for this purpose? Maybe it deserves its own : discussion.
Rules based replica placement can prevent any replica (of any shard, of any collection) from being put on a particular host by ip (or by sys prop set when the node is started) ... https://solr.apache.org/guide/8_6/rule-based-replica-placement.html#do-not-create-any-replicas-in-host-192-45-67-3 ...similar restrictions can easily be imposed by an autoscaling policy rules (although AFAIK you have to flip the logic: "all replicas of all collections should only live on nodes with prop X") ... https://solr.apache.org/guide/8_6/solrcloud-autoscaling-policy-preferences.html#node-selector [ { "replica": "#ALL", "nodeset": {"sysprop.use_for_replicas": "search"}} ] } }' ... but I don't know how much of this functionality has survived "The Great Autoscaling Purge of 9.x" -Hoss http://www.lucidworks.com/
