Frankly, you're into somewhat uncharted waters, the whole lazy core capability was designed for non-cloud mode.
Cores are initialized when the first request comes in that addresses the core. Whether ZK and SolrCloud know a core is active before the first time it's loaded I don't know. I think you'll find that combining lazy core loading with SolrCloud will have more issues, you've found two so far and no doubt there are more lurking. If you'd like to help make SolrCloud work with transient cores, patches welcome! I won't have time/motivation to work on this for the foreseeable future, I'm not even sure it _should_ be supported. So if all you need to do is wait for a while, you have a work-around. Otherwise, I'm clueless. Best Erick On Mon, Aug 12, 2013 at 8:54 AM, Srivatsan <ranjith.venkate...@gmail.com>wrote: > Hi > I manually edited core.properties file by setting /loadOnStartup=false/ on > all cores. But here i am facing a problem. After starting the solr cloud > servers, I couldnt index to any collection till particular interval. I am > getting exception like "No Live Solr Servers". > > => If we submit a index request why does the cores didnt initialize at run > time? > > => How the cores will be initialized if loadOnStartup=false? > > > Thanks > > Srivatsan > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Collection-loadOnStartup-tp4082531p4083972.html > Sent from the Solr - User mailing list archive at Nabble.com. >
