[
https://issues.apache.org/jira/browse/SOLR-14985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871209#comment-17871209
]
ASF subversion and git services commented on SOLR-14985:
--------------------------------------------------------
Commit 90531946281a8ae63b6292f1412059a2063d2279 in solr's branch
refs/heads/branch_9x from aparnasuresh85
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=90531946281 ]
SOLR-14985: CloudSolrClient with Solr URLs wasn't caching state (#2571)
Solrj CloudSolrClient with Solr URLs had serious performance regressions (since
the beginning?) in which its collection state cache was not being used,
resulting in many extra requests to Solr for cluster information. (Aparna
Suresh, shalin, David Smiley)
Co-authored-by: Shalin Shekhar Mangar <sha...@apache.org>
(cherry picked from commit 88fa6208c0f2b8cf4b936295940bbe4b39cb778c)
> 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: 9h 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
