Timothy Potter created SOLR-14987:
-------------------------------------
Summary: SolrStream ends up creating a new HttpSolrClient for
every replica being queried instead of reusing for the same node
Key: SOLR-14987
URL: https://issues.apache.org/jira/browse/SOLR-14987
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: streaming expressions
Reporter: Timothy Potter
Assignee: Timothy Potter
Looking into some streaming expression performance issues when there are many
collections with many shards being queried and I found that SolrStream's open
method creates a new \{{HttpSolrClient}} for every replica being queried. For
instance, in my test case, I have 10 collections with 100 shards each (rf=1)
and I get 1000 HttpSolrClient instances in my SolrClientCache. If I reuse
HttpSolrClient's per node hosting a replica (so 10 in my case), the query time
for my expression drops by half (not too mention the reduced allocation load on
the JVM).
--
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
