You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2012/09/09 07:15:07 UTC
[jira] [Created] (SOLR-3813) When a new leader syncs, we need to
ask all shards to sync back, not just those that are active.
Mark Miller created SOLR-3813:
---------------------------------
Summary: When a new leader syncs, we need to ask all shards to sync back, not just those that are active.
Key: SOLR-3813
URL: https://issues.apache.org/jira/browse/SOLR-3813
Project: Solr
Issue Type: Bug
Components: SolrCloud
Reporter: Mark Miller
Assignee: Mark Miller
Fix For: 4.0, 5.0
Otherwise there is a race where a shard can complete recovery against the old leader and publish as active, while missing the sync stage with the leader - resulting in possible lost updates and shard inconsistency.
--
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
[jira] [Updated] (SOLR-3813) When a new leader syncs, we need to
ask all shards to sync back, not just those that are active.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-3813:
------------------------------
Priority: Critical (was: Major)
we should also ask all shards to sync to us initially, not just active shards - better that than rely on cluster state which can be slightly stale.
> When a new leader syncs, we need to ask all shards to sync back, not just those that are active.
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-3813
> URL: https://issues.apache.org/jira/browse/SOLR-3813
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.0, 5.0
>
>
> Otherwise there is a race where a shard can complete recovery against the old leader and publish as active, while missing the sync stage with the leader - resulting in possible lost updates and shard inconsistency.
--
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
[jira] [Resolved] (SOLR-3813) When a new leader syncs, we need to
ask all shards to sync back, not just those that are active.
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-3813.
-------------------------------
Resolution: Fixed
> When a new leader syncs, we need to ask all shards to sync back, not just those that are active.
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-3813
> URL: https://issues.apache.org/jira/browse/SOLR-3813
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.0, 5.0
>
>
> Otherwise there is a race where a shard can complete recovery against the old leader and publish as active, while missing the sync stage with the leader - resulting in possible lost updates and shard inconsistency.
--
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