[
https://issues.apache.org/jira/browse/SOLR-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403348#comment-15403348
]
Hoss Man commented on SOLR-9366:
--------------------------------
bq. That being said, we can improve a few things:
Add to that list "replicas which know they are not active can response with
{{503 Service Unavailable}}" ... which is what I thought replicas were already
suppose to be doing in situations like this.
I understand that not every client can immediately/magically know that replicas
which are in recovery shouldn't be queried -- my concern is that replicas which
_do_ know for a fact that they are in recovery and are inconsistent with their
leader are happily participating in queries knowing that they are returning
incorrect results.
> replicas in LIR seem to still be participating in search requests
> -----------------------------------------------------------------
>
> Key: SOLR-9366
> URL: https://issues.apache.org/jira/browse/SOLR-9366
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Attachments: SOLR-9366.txt.gz
>
>
> Spinning this off from SOLR-9363 where sarowe's jenkins encountered a strange
> test failure when TestInjection is used causing replicas to return errors on
> some requests.
> Reading over the logs it appears that when this happens, and the replicas are
> put into LIR they then ignore an explicit user requested commit (ie:
> {{Ignoring commit while not ACTIVE - state: BUFFERING replay: false}}) but
> still participate in queries -- apparently before they finish recovery (or at
> the very least before / with-out doing the commit/openSearcher that they
> previously ignored.
> Details and logs to follow...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
