You really should be careful about optimizes, they're generally not needed. And optimizing is almost always wrong when done after every N documents in a batch process. Do it at the very end or not at all. optimize essentially re-writes the entire index into a single segment, so you're copying around a lot of data.
And the operations that get done during optimize, which are mainly purging information associated with deleted documents, gets done anyway upon segment merging. Despite it's name, optimize usually has marginal effect, if any, on search speed. Or did you mean commit? FWIW, Erick On Thu, Nov 8, 2012 at 4:05 PM, shreejay <shreej...@gmail.com> wrote: > I managed to re-index my data without issues. I indexed around 2 million > documents in one of the clouds. I did an optimize after every 500k > documents. > > I also changed the Memory settings and assigned only 6gb for Java , and > kept > 10Gb for OS. > > This seems to be working fine as of now. I am not seeing random leader > selections and servers drops. > > Thanks everyone for your inputs. > > --Shreejay > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr4-0-SolrCloud-queries-tp4016825p4019144.html > Sent from the Solr - User mailing list archive at Nabble.com. >
