SolrCloud configuration contains a single shard and 2 Solr servers, therefore one acts as a leader and one as a replica.
Through a series of events(*) I've ended up with one Solr server being in "Active" status and the leader of the shard while the other one in "Recovery failed" status which cannot recover no matter what. It keeps retrying every 600 sec and logs the following error ERROR org.apache.solr.cloud.RecoveryStrategy [RecoveryThread] - Error while trying to recover. core=sample:org.apache.solr.common.SolrException: No registered leader was found after waiting for 4000ms , collection: sample slice: shard1 at org.apache.solr.common.cloud.ZkStateReader.getLeaderRetry(ZkStateReader.java:531) at org.apache.solr.common.cloud.ZkStateReader.getLeaderRetry(ZkStateReader.java:514) at org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:345) at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:247) Does anyone have any idea as to why the replica cannot locate the leader? What is the proposed solution in this case? (*) Sorry for not being able to provide more details but if it's of any help here goes -> SolrCloud fails to start because of write.lock in index folders -> Shutdown servers and remove write.lock files -> Restart Zookeeper ensemble -> Restart Solr servers -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-node-recovery-fails-with-No-registered-leader-was-found-tp4137331.html Sent from the Solr - User mailing list archive at Nabble.com.