[
https://issues.apache.org/jira/browse/SOLR-14985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867350#comment-17867350
]
Aparna Suresh edited comment on SOLR-14985 at 7/21/24 8:56 PM:
---------------------------------------------------------------
I have created a [PR|https://github.com/apache/solr/pull/2571] to address the
performance issues. Since we do not use aliases, this PR does not address any
performance issues related to the HTTP-based CSP attempting to resolve
aliases.The original PR is 4 years old, and the codebase has evolved since
then, which is why a new PR has been raised.
was (Author: JIRAUSER302780):
We intend to switch {{CloudSolrClient}} to use {{HttpClusterStateProvider}} in
our fork. I have created a [PR|https://github.com/apache/solr/pull/2571] to
address the performance issues. Since we do not use aliases, this PR does not
address any performance issues related to the HTTP-based CSP attempting to
resolve aliases.The original PR is 4 years old, and the codebase has evolved
since then, which is why a new PR has been raised.
> Slow indexing and search performance when using HttpClusterStateProvider
> ------------------------------------------------------------------------
>
> Key: SOLR-14985
> URL: https://issues.apache.org/jira/browse/SOLR-14985
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> HttpClusterStateProvider fetches and caches Aliases and Live Nodes for 5
> seconds.
> The BaseSolrCloudClient caches DocCollection for 60 seconds but only if the
> DocCollection is not lazy and all collections returned by
> HttpClusterStateProvider are not lazy which means they are never cached.
> The BaseSolrCloudClient has a method for resolving aliases which fetches
> DocCollection for each input collection. This is an HTTP call with no caching
> when using HttpClusterStateProvider. This resolveAliases method is called
> twice for each update.
> So overall, at least 3 HTTP calls are made to fetch cluster state for each
> update request when using HttpClusterStateProvider. There may be more if
> aliases are involved or if more than one collection is specified in the
> request. Similar problems exist on the query path as well.
> Due to these reasons, using HttpClusterStateProvider causes horrible
> latencies and throughput for update and search requests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
