[
https://issues.apache.org/jira/browse/SOLR-17971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17971.
---------------------------------
Fix Version/s: 10.2
Resolution: Fixed
Thanks Amrit! And for your review Pierre.
> REBALANCELEADERS command is horribly slow with distributed cluster processing
> -----------------------------------------------------------------------------
>
> Key: SOLR-17971
> URL: https://issues.apache.org/jira/browse/SOLR-17971
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 9.0
> Reporter: Pierre Salagnac
> Assignee: Pierre Salagnac
> Priority: Minor
> Labels: pull-request-available
> Fix For: 10.2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Internally, the {{REBALANCELEADERS}} command checks the results of leader
> re-assignment requests by looking at overseer result distributed maps.
> This is done in {{{}RebalanceLeaders.waitAsyncRequests(){}}}.
> When the cluster is configured to run distributed cluster processing (no
> overseer), results of leader re-assignment commands are not stored in these
> map. This makes the parent {{REBALANCELEADERS}} to wait for a long time and
> eventually timeout. Then it continues processing.
> That's unclear to me how the commands actually worked, but it seems leaders
> were correctly rebalanced even in case of a timeout. So there is no big
> functional impact.
> Instead of checking the overseer result maps, the parent command should check
> the requests status by invoking {{REQUESTSTATUS}} for each asynchronous ID.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
