Earlier, you said that optimize is the only way that deleted documents are expunged. That is false. They are expunged when the segment they are in is merged. A forced merge (optimize) merges all segments, so will expunge all deleted document. But those documents will be expunged by merges eventually.
When you have deleted docs in the largest segment, you have to wait for a merge of that segment. My best advice is to stop looking at the deleted documents count and worry about something that makes a difference to your users. For about 10 years, I worked on Ultraseek Server, a search engine with the same design for merging and document deletion. With over 10K installations, we never had a customer who had a problem caused by deleted documents. wunder On Nov 14, 2013, at 7:41 AM, "michael.boom" <my_sky...@yahoo.com> wrote: > Thanks Erick! > > That's a really interesting idea, i'll try it! > Another question would be, when does the merging actually happens? Is it > triggered or conditioned by something? > > Currently I have a core with ~13M maxDocs and ~3M deleted docs, and although > I see a lot of merges in SPM, deleted documents aren't really going > anywhere. > For merging I have the example settings, haven't changed it. > > > > > ----- > Thanks, > Michael > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Optimizing-cores-in-SolrCloud-tp4100871p4100936.html > Sent from the Solr - User mailing list archive at Nabble.com.
