You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Anshum Gupta (JIRA)" <ji...@apache.org> on 2014/09/08 10:22:28 UTC
[jira] [Updated] (SOLR-6379) CloudSolrServer can query the wrong
replica if a collection has a SolrCore name that matches a collection name.
[ https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anshum Gupta updated SOLR-6379:
-------------------------------
Attachment: SOLR-6379.patch
A small optimization to make sure that the querystring is parsed in the DispatchFilter only once.
I am still not sure if we have a consensus on this one though. I don't have a strong opinion but would want to have this resolution issue fixed and biased towards collection name resolution in SolrCloud mode while also have a mechanism to resolve a core if need be.
We should either resolve this or at least in BOLD, specify that a user shouldn't be reusing a core-name to create a collection (or vice-versa) when the core doesn't belong the the very collection.
> CloudSolrServer can query the wrong replica if a collection has a SolrCore name that matches a collection name.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6379
> URL: https://issues.apache.org/jira/browse/SOLR-6379
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Hoss Man
> Assignee: Anshum Gupta
> Priority: Minor
> Fix For: 5.0, 4.10
>
> Attachments: SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.patch, SOLR-6379.pristine_collection.test.patch
>
>
> spin off of SOLR-2894 where sarowe & miller were getting failures from TestCloudPivot that seemed unrelated to any of hte distrib pivot logic itself.
> in particular: adding a call to "waitForThingsToLevelOut" at the start of the test, even before indexing any docs, seemed to work around the problem -- but even if all replicas aren't yet up when the test starts, we should either get a failure when adding docs (ie: no replica hosting the target shard) or queries should only be routed to the replicas that are up and fully caught up with the rest of the collection.
> (NOTE: we're specifically talking about a situation where the set of docs in the collection is static during the query request)
--
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