lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-3813) When a new leader syncs, we need to ask all shards to sync back, not just those that are active.
Date Mon, 10 Sep 2012 22:48:07 GMT

     [ 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


Mime
View raw message