wing:
> 1. don't use warmup
> 2. don't use collation
> 3. don't define spell check for /select, but define a distinct handler and
> call it specifically
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-lo
6.n3.nabble.com/SolrCloud-loop-in-recovery-mode-tp4015330p4015622.html
Sent from the Solr - User mailing list archive at Nabble.com.
It is actually connected to this:
https://gist.github.com/2880527
Once you have collation = true + warmup, the init is stuck on wait
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-loop-in-recovery-mode-tp4015330p4015593.html
Sent from the Solr - User mailing
true, this obviously doesn't happen and the
application starts normally.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-loop-in-recovery-mode-tp4015330p4015581.html
Sent from the Solr - User mailing list archive at Nabble.com.
distributed by
solrcloud.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-loop-in-recovery-mode-tp4015330p4015574.html
Sent from the Solr - User mailing list archive at Nabble.com.
This sounds like two issues. One, you are triggering a leader election
somehow. Do you see session expiration errors in the logs? You may
need to raise the timeout.
The second issue is probably related to what came out of
https://issues.apache.org/jira/browse/SOLR-3939
Shards that have no version
