[
https://issues.apache.org/jira/browse/SOLR-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476487#comment-13476487
]
Joel Bernstein commented on SOLR-3939:
--------------------------------------
I reproduced it again. I pulled again from the top of the 4x branch. I didn't
apply the patch because it was committed, I believe.
Same exact steps as described above. Attached is part of the log file from the
second Solr instance that shows the replica going into recovery. It's looking
for the collection1 core that was unloaded from the first solr instance.
> Solr Cloud recovery and leader election when unloading leader core
> ------------------------------------------------------------------
>
> Key: SOLR-3939
> URL: https://issues.apache.org/jira/browse/SOLR-3939
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0-BETA, 4.0
> Reporter: Joel Bernstein
> Assignee: Mark Miller
> Labels: 4.0.1_Candidate
> Fix For: 4.1, 5.0
>
> Attachments: cloud.log, 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 instance.
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
