You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Pierre Salagnac (Jira)" <ji...@apache.org> on 2025/10/21 13:42:00 UTC
[jira] [Updated] (SOLR-17971) REBALANCELEADERS command is horribly slow with distributed cluster processing
[ https://issues.apache.org/jira/browse/SOLR-17971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Salagnac updated SOLR-17971:
-----------------------------------
Issue Type: Bug (was: Improvement)
Priority: Minor (was: Major)
> 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
> Affects Versions: 9.0
> Reporter: Pierre Salagnac
> Priority: Minor
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org