[
https://issues.apache.org/jira/browse/SOLR-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232906#comment-14232906
]
Noble Paul commented on SOLR-5890:
----------------------------------
Implicit router can work 2 ways.
# Docs reside in the node where it is sent to
# Or use a route as the actual name of the shard
Whenever it is not possible to identify the shard correctly (either using
{{id}} or {{router.field}} ) the requests should be distributed across the
cluster
> 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
>
>
> 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
