[
https://issues.apache.org/jira/browse/SOLR-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694637#comment-17694637
]
David Smiley commented on SOLR-8238:
------------------------------------
Ram even made a good case for balancing leaders even with NRT, and with
concurring agreement from others.
{quote}2> is the REBALANCELEADERS command. But this noticeably impacted
performance in a situation where literally hundreds of replicas on a single
Solr instance were leaders, very special circumstances.
{quote}
[~erickerickson] I'm unsure I follow what you mean. Do you mean that a node
coming up had hundreds of replicas with the "preferredLeader" flag, and once
upon a time this was aggressively honored to issue REBALANCE_LEADERS on
startup, all concurrently even (or something equivalent)? That is an approach
I was thinking, so if you don't mean this, I can't tell yet if your anecdote
actually applies to wether this is a sound idea or not.
_(not anticipating a response from Erick who has since retired... but maybe
others have awareness)_
> Make Solr respect preferredLeader at startup
> --------------------------------------------
>
> Key: SOLR-8238
> URL: https://issues.apache.org/jira/browse/SOLR-8238
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 5.2.1
> Reporter: Peter Morgan
> Priority: Minor
>
> After setting preferredLeader property, noticed that upon restarting leaders
> revert to wherever they were previously running before REBALANCE was called.
> I would expect the preferredLeader to influence the startup election, but it
> appears it is not observed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
