[
https://issues.apache.org/jira/browse/SOLR-10780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846106#comment-17846106
]
David Smiley commented on SOLR-10780:
-------------------------------------
I'd rather see leadership be sticky (e.g. via preferredLeader), maybe even by
default, rather than having to explicitly rebalance. Thus a "preferred" leader
would recognize itself to be such (e.g. due to explicit assignment and/or
perhaps something automatic TBD), and seek to become the leader on its own
(e.g. on becoming state=ACTIVE) without anything more heavyweight as this issue
describes.
> A new collection property autoRebalanceLeaders
> -----------------------------------------------
>
> Key: SOLR-10780
> URL: https://issues.apache.org/jira/browse/SOLR-10780
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Noble Paul
> Priority: Major
>
> In solrcloud , the first replica to get started in a given shard becomes the
> leader of that shard. This is a problem during cluster restarts. the first
> node to get started have al leaders and that node ends up being very heavily
> loaded. The solution we have today is to invoke a REBALANCELEADERS command
> explicitly so that the system ends up with a uniform distribution of leaders
> across nodes. This is a manual operation and we can make the system do it
> automatically.
> so each collection can have an {{autoRebalanceLeaders}} flag . If it is set
> to true whenever a replica becomes {{ACTIVE}} in a shard , a
> {{REBALANCELEADER}} is invoked for that shard
--
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
