ick Erickson
> Sent: Wednesday 10th January 2018 22:41
> To: solr-user
> Subject: Re: Very high number of deleted docs, part 2
>
> There's some background here:
> https://lucidworks.com/2017/10/13/segment-merging-deleted-documents-optimize-may-bad/
>
> the 2.5 "live&
;
> > > How about optimizing it again, with maxSegments set to ten, it should
> > > recover right?
> > >
> > > -Original message-
> > > > From:Shawn Heisey
> > > > Sent: Friday 5th January 2018 14:34
> > > > To:
> Subject: Re: Very high number of deleted docs, part 2
>
> I'm not 100% sure that playing with maxSegments will work.
>
> what will work is to re-index everything. You can re-index into the
> existing collection, no need to start with a new collection. Eventually
> you
izing it again, with maxSegments set to ten, it should
> recover right?
>
> -Original message-
> > From:Shawn Heisey
> > Sent: Friday 5th January 2018 14:34
> > To: solr-user@lucene.apache.org
> > Subject: Re: Very high number of deleted docs, part
4
> To: solr-user@lucene.apache.org
> Subject: Re: Very high number of deleted docs, part 2
>
> On 1/5/2018 5:33 AM, Markus Jelsma wrote:
> > Another collection, now on 7.1, also shows this problem and has default TMP
> > settings. This time size is different, each shard of t
On 1/5/2018 5:33 AM, Markus Jelsma wrote:
Another collection, now on 7.1, also shows this problem and has default TMP
settings. This time size is different, each shard of this collection is over 40
GB, and each shard has about 50 % deleted documents. Each shard's largest
segment is just under
