[jira] [Commented] (SOLR-5890) Delete silently fails if not sent to shard where document was added

["Mark Miller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941862#comment-13941862 ] 

Mark Miller commented on SOLR-5890:
-----------------------------------

Very strange - the request should be forwarded. This will be interesting.

> Delete silently fails if not sent to shard where document was added
> -------------------------------------------------------------------
>
>                 Key: SOLR-5890
>                 URL: https://issues.apache.org/jira/browse/SOLR-5890
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.7
>         Environment: Debian 7.4.
>            Reporter: Peter Inglesby
>             Fix For: 4.8, 5.0, 4.7.1
>
>
> We have SolrCloud set up with two shards, each with a leader and a replica.  We use haproxy to distribute requests between the four nodes.
> Regardless of which node we send an add request to, following a commit, the newly-added document is returned in a search, as expected.
> However, we can only delete a document if the delete request is sent to a node in the shard where the document was added.  If we send the delete request to a node in the other shard (and then send a commit) the document is not deleted.  Such a delete request will get a 200 response, with the following body:
>   {'responseHeader'=>{'status'=>0,'QTime'=>7}}
> Apart from the the very low QTime, this is indistinguishable from a successful delete.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org