[
https://issues.apache.org/jira/browse/SOLR-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878217#comment-13878217
]
Mark Miller commented on SOLR-5650:
-----------------------------------
Just saw another fail where the control had a doc the cluster did not. This
issue may have helped hide it previously, don't remember seeing it before.
Actually looks like a legit fail. Looks like a single leader in a shard
accepted an update and was killed. The update is gone, and so the loss makes
sense in the current system. You need support for the param that tells how many
replicas to the update must get to for success to protect against this.
> When mixing adds and deletes, it appears there is a corner case where
> peersync can bring back a deleted update.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5650
> URL: https://issues.apache.org/jira/browse/SOLR-5650
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 5.0, 4.7
>
> Attachments: SOLR-5650.patch, SOLR-5650.patch, solr.log.tar.gz
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
