You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2015/11/04 20:11:27 UTC
[jira] [Resolved] (SOLR-8215) SolrCloud can select a core not in
active state for querying
[ https://issues.apache.org/jira/browse/SOLR-8215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Thacker resolved SOLR-8215.
---------------------------------
Resolution: Fixed
Assignee: Varun Thacker
Fix Version/s: 5.4
Thanks Mark for the review!
> SolrCloud can select a core not in active state for querying
> ------------------------------------------------------------
>
> Key: SOLR-8215
> URL: https://issues.apache.org/jira/browse/SOLR-8215
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Fix For: 5.4
>
> Attachments: SOLR-8215.patch, SOLR-8215.patch
>
>
> A query can be served by a core which is not in active state if the request hits the node which hosts these non active cores.
> We explicitly check for only active cores to search against in {{CloudSolrClient#sendRequest}} Line 1043 on trunk.
> But we don't check this if someone uses the REST APIs
> {{HttpSolrCall#getCoreByCollection}} should only pick cores which are active on line 794 on trunk.
> We however check it on line 882/883 in HttpSolrCall, when we try to find cores on other nodes when it's not present locally.
> So let's fix {{HttpSolrCall#getCoreByCollection}} to make the active check as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org