Shalin Shekhar Mangar created SOLR-14985:
--------------------------------------------
Summary: 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
Security Level: Public (Default Security Level. Issues are Public)
Components: SolrJ
Reporter: Shalin Shekhar Mangar
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 requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
