Note there is a threshold to expungeDeletes such that if there aren't enough deletes in a segment relative to the docs in that segments, it won't do any expunging.
On Thu, Aug 11, 2016 at 11:51 AM Shawn Heisey <[email protected]> wrote: > On 8/11/2016 6:27 AM, Michael McCandless wrote: > > You could explore this idea using a custom MergePolicy? > > > > That would let you run perf. tests on the 35 GB index, comparing > > forceMerge, expungeDeletes (TMP), and expungeDeletes (your new > > MergePolicy). > > That's an interesting idea. I can attempt that, but I must admit up > front that I might not be able to figure out how to write it. > > Somebody asked me privately how the idea I'm proposing would be > different than the existing expungeDeletes functionality. I don't > really know how it would be different, but I do know that when I send a > commit with expungeDeletes set to true, the number of deletes in the > index hasn't changed when it finishes, which happens just as quickly as > a regular commit. That's why I started thinking about this approach. > > I've seen occasional questions on the Solr list and in the IRC channel > about how to get rid of deleted documents without waiting for a full > optimize/forceMerge, so I think there's a demand for the functionality. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker LinkedIn: http://linkedin.com/in/davidwsmiley | Book: http://www.solrenterprisesearchserver.com
