Sachin Goyal created SOLR-6832:
----------------------------------
Summary: Queries be served locally rather than being forwarded to
another replica
Key: SOLR-6832
URL: https://issues.apache.org/jira/browse/SOLR-6832
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.10.2
Reporter: Sachin Goyal
Currently, I see that code flow for a query in SolrCloud is as follows:
For distributed query:
SolrCore -> SearchHandler.handleRequestBody() -> HttpShardHandler.submit()
For non-distributed query:
SolrCore -> SearchHandler.handleRequestBody() -> QueryComponent.process()
\\
\\
\\
For a distributed query, the request is always sent to all the shards even if
the originating SolrCore (handling the original distributed query) is a replica
of one of the shards.
If the original Solr-Core can check itself before sending http requests for any
shard, we can probably save some network hopping and gain some performance.
\\
\\
We can change SearchHandler.handleRequestBody() or HttpShardHandler.submit() to
fix this behavior (most likely the former and not the latter).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
