You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Andrzej Bialecki (Jira)" <ji...@apache.org> on 2021/08/03 13:47:00 UTC
[jira] [Resolved] (SOLR-15565) Optimize CLUSTERSTATUS when
filtering by collection
[ https://issues.apache.org/jira/browse/SOLR-15565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki resolved SOLR-15565.
-------------------------------------
Resolution: Invalid
It turns out this is already the case, ie. when {{collection}} param is used then only this collection is retrieved from {{ClusterState}}.
> Optimize CLUSTERSTATUS when filtering by collection
> ---------------------------------------------------
>
> Key: SOLR-15565
> URL: https://issues.apache.org/jira/browse/SOLR-15565
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
>
> When user specifies {{collection}} parameter in the {{CLUSTERSTATUS}} command one would expect that Solr retrieves and materializes only that collection state. Unfortunately, {{ClusterStatus.getClusterStatus}} retrieves the complete map, which in turn materializes all collection statuses. On large clusters with many large collections this is wasteful.
> In this case, when user requests state information for some collection only, we should iterate just on the collection names and materialize only these collections' information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org