[
https://issues.apache.org/jira/browse/SOLR-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101290#comment-14101290
]
Mark Miller commented on SOLR-6379:
-----------------------------------
bq. AliasIntegrationTest currently fails.
That makes it tricky. We kind of need that behevaior. This was introduced in
the bug fix for SOLR-5380.
bq. I think it would make sense to consider zkawareness more openly in the
DispatchFilter to redirect queries to the correct collection.
Okay, now I think I've caught up with what you meant. I think you are right.
Perhaps we just have to favor collection over core when resolving. I struggled
with this when I put it in - which do you resolve first. I just kind of took
the easier path by default. Let's see what happens when you try and change it.
> 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: Mark Miller
> Attachments: SOLR-6379.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
