Please don't do that ;) Unless you're willing to do it frequently. See: https://lucidworks.com/2017/10/13/segment-merging-deleted-documents-optimize-may-bad/
expungeDeletes is really a variety of optimize, so the issues outlined in that blog apply. Best, Erick On Thu, Nov 9, 2017 at 12:24 PM, Shashank Pedamallu <spedama...@vmware.com> wrote: > Thanks for the response Erick. I’m deleting the documents with expungeDeletes > option set as true. So, that does trigger a merge to throw away the deleted > documents. > > On 11/9/17, 12:17 PM, "Erick Erickson" <erickerick...@gmail.com> wrote: > > bq: Is there a way to distinguish between when size is being reduced > because of a delete from that of during a lucene merge. > > Not sure what you're really looking for here. Size on disk is _never_ > reduced by a delete operation, the document is only 'marked as > deleted'. Only when segments are merged are the resources reclaimed, > i.e. the index gets smaller. You can figure out what % of your index > consists of deleted documents by the delta between numDocs and > maxDocs, available on the admin UI and from the Luke handler (and > maybe JMX). > > Best, > Erick > > On Thu, Nov 9, 2017 at 12:06 PM, Shashank Pedamallu > <spedama...@vmware.com> wrote: > > Hi, > > > > I wanted to get accurate metrics regarding to the amount of data being > indexed in Solr. In this regard, I observe that sometimes, this number > decreases due to lucene merges. But I’m also deleting data at times. Is there > a way to distinguish between when size is being reduced because of a delete > from that of during a lucene merge. > > > > Thanks, > > Shashank > >
