[
https://issues.apache.org/jira/browse/SOLR-10780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-10780:
------------------------------
Description:
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
was:
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 collection
> A new collection property autoRebalanceLeaders
> -----------------------------------------------
>
> Key: SOLR-10780
> URL: https://issues.apache.org/jira/browse/SOLR-10780
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Noble Paul
>
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
