I discussed this issue offline with David, and I'm now working on a code
change to make the preferredLeader to become the leader when we register a
replica.
The idea is, when we register a replica from Zookeeper, we check whether it
has the preferred leader flag. When true, we tell the current lea
I found this existing issue:
https://issues.apache.org/jira/browse/SOLR-8238
I commented on it just now. Erick isn't around anymore but I'd appreciate
input from anyone using "preferredLeader".
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Mon, Fe
Seems like a bug to me!
Recommended reading: https://issues.apache.org/jira/browse/SOLR-6491
There's a treasure trove of information in JIRA to learn about how code
comes to be; what were the intentions behind features; what alternatives
were explored; pros & cons.
~ David Smiley
Apache Lucene/Sol
It should also be possible to set preferred leaders during shard split.
Currently, shard split always keeps the current host as the leader of the
sub-shards. And if we split again sub-shards, this can lead to a very
unbalanced situation where the same host becomes the leader for a whole set
of shar
I'm not yet sure if preferredLeader is honored after a restart of the node
that has this state; though it'd be easy to see. I plan to observe this
empirically soon. If memory serves, I recall leader checks occur for each
replica on a node's start. One would think this would respect
preferredLead
We have the new Replica Placement API, which can react to various events like
nodeUp, nodeDown etc.
Would it make sense to auto rebalance leaders after a certain delay after the
last nodeDown/Up event occurred?
Jan
> 22. sep. 2022 kl. 05:23 skrev David Smiley :
>
> SolrCloud's choice of a lead
