Or, don't "optimize" (force merge) at all. Really. This is a manual override for an automatic process, merging.
I can only think of one case where a forced merge makes sense: 1. All documents are reindexed. 2. Traditional Solr replication is used (not SolrCloud). 3. Replication is manually timed to be after the forced merge. For incremental indexing with replication, a forced merge will cause a huge amount of disk and network traffic. wunder Former search guy for Netflix Current search guy for Chegg On Nov 4, 2012, at 12:02 PM, tictacs wrote: > Thanks for the reply both and apologies if this is a recurring question. > From the sounds of it I am sure an optimize overnight when app traffic is > low will suffice. This will massively help with server perfomance I am > sure. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Disk-writes-and-set-up-suggestions-tp4018031p4018134.html > Sent from the Solr - User mailing list archive at Nabble.com.
