not practical for
me because of the JDK 1.7 requirement).
Thanks
Yann
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-node-recovery-fails-with-No-registered-leader-was-found-tp4137331p4166601.html
Sent from the Solr - User mailing list archive at Nabble.com.
java.lang.Thread.run(Thread.java:744)
{code}
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-node-recovery-fails-with-No-registered-leader-was-found-tp4137331p4157312.html
Sent from the Solr - User mailing list archive at Nabble.com.
ling server
managed to "recover" the index successfully.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-node-recovery-fails-with-No-registered-leader-was-found-tp4137331p4137584.html
Sent from the Solr - User mailing list archive at Nabble.com.
utdown 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.
ny 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
