You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ishan Chattopadhyaya (JIRA)" <ji...@apache.org> on 2015/01/03 19:38:34 UTC
[jira] [Comment Edited] (SOLR-5890) Delete silently fails if not
sent to shard where document was added
[ https://issues.apache.org/jira/browse/SOLR-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263581#comment-14263581 ]
Ishan Chattopadhyaya edited comment on SOLR-5890 at 1/3/15 6:37 PM:
--------------------------------------------------------------------
Updated the patch with the above TODO item. This patch now has:
1. deleteById command now has a _route_ parameter.
2. commitWithin wasn't working (at least with the implicit router). Added a fix in SolrCmdDistributor.
3. deleteById command (implicit router) should be distributed to all shard leaders if no _route_ parameter is present.
[~noble.paul], [~shalinmangar], please review (review request https://reviews.apache.org/r/29561/).
was (Author: ichattopadhyaya):
Updated the patch with the above TODO item. This patch now has:
1. deleteById command now has a _route_ parameter.
2. commitWithin wasn't working (at least with the implicit router). Added a fix in SolrCmdDistributor.
3. deleteById command (implicit router) should be distributed to all shard leaders if no _route_ parameter is present.
[~noble.paul], [~shalinmangar], please review.
> 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, SOLR-5890.patch, SOLR-5890.patch, SOLR-5980.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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org