You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Commit Tag Bot (JIRA)" <ji...@apache.org> on 2013/05/10 08:57:18 UTC
[jira] [Commented] (SOLR-4795) Sub shard leader should not accept
any updates from parent after it goes active
[ https://issues.apache.org/jira/browse/SOLR-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653593#comment-13653593 ]
Commit Tag Bot commented on SOLR-4795:
--------------------------------------
[lucene_solr_4_3 commit] shalin
http://svn.apache.org/viewvc?view=revision&revision=1480895
SOLR-4795: Sub shard leader should not accept any updates from parent after it goes active
> Sub shard leader should not accept any updates from parent after it goes active
> -------------------------------------------------------------------------------
>
> Key: SOLR-4795
> URL: https://issues.apache.org/jira/browse/SOLR-4795
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.3
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 4.4
>
> Attachments: SOLR-4795.patch
>
>
> The sub shard leaders accept any update from a parent as long as their range is a subset of parent's range. A sub shard can continue to accept updates from parent even after it has gone active which can lead to inconsistencies. This affects partial updates (think counters) the most but can also lead to out-of-order updates to the same document.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org