[ https://issues.apache.org/jira/browse/SOLR-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya updated SOLR-9594: --------------------------------------- Fix Version/s: (was: 6.4) 6.5 > Query requests to one shard collections can switch to two-phase distributed > search if they hit a node in recovery > ----------------------------------------------------------------------------------------------------------------- > > Key: SOLR-9594 > URL: https://issues.apache.org/jira/browse/SOLR-9594 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: search, SolrCloud > Affects Versions: 4.10.4, 5.5.3, 6.2.1 > Reporter: Shalin Shekhar Mangar > Labels: difficulty-medium, impact-medium > Fix For: 6.5, master (7.0) > > > All search requests in SolrCloud are distributed two-phase requests by > default but Solr short-circuits it to the local replica/core if the > collection has numShards=1 and the local replica/core is active. > But if the request happens to land on a replica which isn't active, the > short-circuiting doesn't happen and the local replica/core which isn't active > becomes the aggregator for a proper two-phase distributed request. If the > search components involved in the request do not support distributed search > then you can have weird results in such cases. This behavior is very > surprising because most of the times queries are short circuited and behave > as if they were non-distrib queries. > We could either: > # Forward the request to some other node entirely or > # Make a call with distrib=false to another node -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org