lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] [Updated] (SOLR-5890) Delete silently fails if not sent to shard where document was added
Date Tue, 02 Sep 2014 06:24:21 GMT


Shalin Shekhar Mangar updated SOLR-5890:
    Labels: difficulty-medium impact-medium workaround-exists  (was: )

> Delete silently fails if not sent to shard where document was added
> -------------------------------------------------------------------
>                 Key: SOLR-5890
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.7
>         Environment: Debian 7.4.
>            Reporter: Peter Inglesby
>              Labels: difficulty-medium, impact-medium, workaround-exists
>             Fix For: 4.9, 5.0
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message