Hi Shawn, This gives me a good understanding. However, I think that slowness in start-up in my case is due to segmentation. Before restarting my index contains 42 segments with 30GB. After restarting, index is in one segment with 22GB. So, I think that shard unavailability is coming from optimization process which is executed when we restart solr.
Is there any option is solr to avoid this implicit optimization on startup? What I learned from this experience is that we need to do explicit optimization in regular period to avoid a huge number of segments. Is it a best practice in solr? Regards, Nabil. Le Dimanche 12 octobre 2014 22h03, Shawn Heisey <apa...@elyograg.org> a écrit : On 10/12/2014 12:46 PM, nabil Kouici wrote: > I'm evaluating solr performance. I've created implicit collection with 2 > shards in different server. first shard contains 100 million documents > (30GB), second contain one million document.When I restart the second solr > instance, shard become immediately available. However, when I restart the > first solr, shard with 100 million doc take a huge time to be available for > search. Is it normal? In Cloud interface, shard is green (Active). My servers > have 28GB RAM. > I'm using default solrconfig.xml. Does the following URL describe the problem you're running into? http://wiki.apache.org/solr/SolrPerformanceProblems#Slow_startup Thanks, Shawn
