[
https://issues.apache.org/jira/browse/SOLR-17381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17381.
---------------------------------
Fix Version/s: 9.8
Resolution: Fixed
Thanks for contributing!
I wondered more about the V2 API situation here. I found it and it's already
decomposed as we want (done in SOLR-15748); I wish I had seen this before!
(face-palm). Granted, the approach taken here was very backwards compatible so
that we could modify SolrJ HttpClusterStateProvider to continue to use a V1 API
that would still function talking to some older Solr server or one that didn't
have V2 enabled.
> Make CLUSTERSTATUS request configurable
> ---------------------------------------
>
> Key: SOLR-17381
> URL: https://issues.apache.org/jira/browse/SOLR-17381
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Aparna Suresh
> Priority: Minor
> Labels: pull-request-available
> Fix For: 9.8
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> Fetching {{CLUSTERSTATUS}} remotely is resource-intensive and should be done
> with caution. Currently, if no parameters are specified, the call returns all
> information, including collections, shards, replicas, aliases, cluster
> properties, roles, and more. This can have significant performance
> implications for clients using a Solr cluster with thousands of collections.
> Several performance [issues|https://issues.apache.org/jira/browse/SOLR-14985]
> have been identified when switching {{CloudSolrClient}} to use HTTP-based
> CSP, particularly in two instances where the entire cluster state is fetched
> unnecessarily.
> *Proposal:* Modify the requests to retrieve only the necessary information,
> such as the cluster status for a specific collection, live nodes, or cluster
> properties. Ensure these changes maintain backward compatibility.
> Additionally, update the HTTP CSP to reflect these optimizations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
