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

Ishan Chattopadhyaya edited comment on SOLR-5890 at 12/5/14 6:35 AM:
---------------------------------------------------------------------

[~shalinmangar] Yes, I tested it (patch attached for the test). Here, as far as 
I understand, since the router is implicit, there is no hashing of the id 
performed to find the right shard; instead the deleteById is performed on the 
shard to which the update request is sent to (unless a specific _route_ param 
is present). Maybe I'm missing something?


was (Author: ichattopadhyaya):
[~shalinmangar] Yes, I tested it (patch attached for the test). Here, as far as 
I understand, since the router is implicit, there is no hashing of the id 
performed to find the right shard; instead the deleteById is performed on the 
shard to which the update request is sent to (unless a specific _route_ param 
is present).

> 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
>            Assignee: Noble Paul
>              Labels: difficulty-medium, impact-medium, workaround-exists
>             Fix For: 5.0, Trunk
>
>         Attachments: 5890_tests.patch
>
>
> 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.3.4#6332)

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

Reply via email to