lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3939) Solr Cloud recovery and leader election when unloading leader core
Date Sun, 21 Oct 2012 18:14:12 GMT


Yonik Seeley commented on SOLR-3939:

Actually, even if we someday replicate recent versions along with the index (by adding them
to the commitData in the index, etc), it may still be good to support indexes w/o version
info.  On the other side of the spectrum from having indexing completely automated, some people
may want the ability to create a new shard off-line and then insert it into the cluster as
> Solr Cloud recovery and leader election when unloading leader core
> ------------------------------------------------------------------
>                 Key: SOLR-3939
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0-BETA, 4.0
>            Reporter: Joel Bernstein
>            Assignee: Mark Miller
>            Priority: Critical
>              Labels: 4.0.1_Candidate
>             Fix For: 4.1, 5.0
>         Attachments: cloud2.log, cloud.log, SOLR-3939.patch, SOLR-3939.patch
> When a leader core is unloaded using the core admin api, the followers in the shard go
into recovery but do not come out. Leader election doesn't take place and the shard goes down.
> This effects the ability to move a micro-shard from one Solr instance to another Solr
> The problem does not occur 100% of the time but a large % of the time. 
> To setup a test, startup Solr Cloud with a single shard. Add cores to that shard as replicas
using core admin. Then unload the leader core using core admin. 

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message