[
https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101113#comment-14101113
]
Mark Miller commented on SOLR-6379:
-----------------------------------
This looks like it's simply one of those corner case bugs that manifests when
you have a collection that has core names that match another collection name.
I'm glad we actually kind of randomly ended up with our tests this way because
it catches great stuff.
control_collection
collection1
collection1
collection_shard1_replica1
etc
There must be some code that is keying on core name and not taking into account
the collection level like it should.
> new replicas seem to be involved in queries before they are ready
> -----------------------------------------------------------------
>
> Key: SOLR-6379
> URL: https://issues.apache.org/jira/browse/SOLR-6379
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Anshum Gupta
> Attachments: SOLR-6379.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
