[
https://issues.apache.org/jira/browse/SOLR-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706307#comment-15706307
]
Varun Thacker commented on SOLR-9707:
-------------------------------------
Its still a good idea to filter out down replica before sending the update.
There might be edge cases / bugs which could lead to a replica being in down
state even on a live node.
The tests pass with Jessica's original patch.
[~markrmil...@gmail.com] or [~ysee...@gmail.com] any suggestions on how we can
add a test case for this or is it just safe to commit the patch without an
explicit test case for it?
> DeleteByQuery forward requests to down replicas and set it in LiR
> -----------------------------------------------------------------
>
> Key: SOLR-9707
> URL: https://issues.apache.org/jira/browse/SOLR-9707
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: Jessica Cheng Mallet
> Assignee: Varun Thacker
> Labels: solrcloud
> Attachments: SOLR-9707.diff, SOLR-9707.patch
>
>
> DeleteByQuery, unlike other requests, does not filter out the down replicas.
> Thus, the update is still forwarded to the down replica and fails, and the
> leader then sets the replica in LiR. In a cluster where there are lots of
> deleteByQuery requests, this can flood the /overseer/queue.
--
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
