[
https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112622#comment-14112622
]
Mark Miller edited comment on SOLR-6379 at 8/27/14 6:43 PM:
------------------------------------------------------------
bq. core create WILL NOT work in legacyCloud=false.
Huh?
bq. Nevertheless, it is desirable to fix our tests to match with more real
world use cases
I'm not so worried about that.
For one, we ship our configs much like the configs being tested - it's more
real world than you would like to believe. Also, we test many other scenarios
more real world scenarios already. I'm glad we also have something that can
catch this ugly corner case so that we can address it. Adding coverage is
great, but losing coverage sucks.
was (Author: [email protected]):
bq. core create WILL NOT work in legacyCloud=false.
Huh?
bq. Nevertheless, it is desirable to fix our tests to match with more real
world use cases
I'm not so worried about that.
For one, we ship our configs much like the configs be tested - it's more real
world than you would like to believe. Also, we test many other scenarios more
real world scenarios already. I'm glad we also have something that can catch
this ugly corner case so that we can address it. Adding coverage is great, but
losing coverage sucks.
> 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.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.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
