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
arkus
[1]
http://lucene.472066.n3.nabble.com/Very-high-number-of-deleted-docs-td4357327.html
Well, that made a difference! Now we're back at 64 MB per replica.
Thanks,
Markus
-Original message-
> From:Erick Erickson
> Sent: Wednesday 4th October 2017 16:19
> To: solr-user
> Subject: Re: Very high number of deleted docs
>
> Hmmm, OK, I stand corr
the periodic update cycle, but
> i preferred Lucene to do it for me.
>
> Thanks,
> Markus
>
> -Original message-
>> From:Erick Erickson
>> Sent: Wednesday 4th October 2017 14:56
>> To: solr-user
>> Subject: Re: Very high number of deleted docs
>
iodic update cycle, but i
preferred Lucene to do it for me.
Thanks,
Markus
-Original message-
> From:Erick Erickson
> Sent: Wednesday 4th October 2017 14:56
> To: solr-user
> Subject: Re: Very high number of deleted docs
>
> Did you _ever_ do a forceMerge/optimize or expu
Ah thanks for that!
-Original message-
> From:Emir Arnautović
> Sent: Wednesday 4th October 2017 15:03
> To: solr-user@lucene.apache.org
> Subject: Re: Very high number of deleted docs
>
> Hi Markus,
> It is passed but not explicitly - it uses reflection to pass
is just that i am actually very surprised this can
>> happen at all with default settings. This factory, unfortunately does not
>> seem to support settings configured in solrconfig.
>>
>> Thanks,
>> Markus
>>
>> -Original message-----
>>>
rkus
>
> -Original message-
>> From:Amrit Sarkar
>> Sent: Wednesday 4th October 2017 14:42
>> To: solr-user@lucene.apache.org
>> Subject: Re: Very high number of deleted docs
>>
>> Hi Markus,
>>
>> Emir already mentioned tuning *reclaimDeletesWei
en at all with default settings. This factory, unfortunately does not
> seem to support settings configured in solrconfig.
>
> Thanks,
> Markus
>
> -Original message-
>> From:Amrit Sarkar
>> Sent: Wednesday 4th October 2017 14:42
>> To: solr-user@lucene.a
-Original message-
> From:Amrit Sarkar
> Sent: Wednesday 4th October 2017 14:42
> To: solr-user@lucene.apache.org
> Subject: Re: Very high number of deleted docs
>
> Hi Markus,
>
> Emir already mentioned tuning *reclaimDeletesWeight which *affects segments
&
ct: Re: Very high number of deleted docs
>
> Hi Markus,
> You can set reclaimDeletesWeight in merge settings to some higher value than
> default (I think it is 2) to favor segments with deleted docs when merging.
>
> HTH,
> Emir
> --
> Monitoring - Log Managemen
Hi Markus,
Emir already mentioned tuning *reclaimDeletesWeight which *affects segments
about to merge priority. Optimising index time by time, preferably
scheduling weekly / fortnight / ..., at low traffic period to never be in
such odd position of 80% deleted docs in total index.
Amrit Sarkar
Se
Hi Markus,
You can set reclaimDeletesWeight in merge settings to some higher value than
default (I think it is 2) to favor segments with deleted docs when merging.
HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sem
Hello,
Using a 6.6.0, i just spotted one of our collections having a core of which
over 80 % of the total number of documents were deleted documents.
It has configured with no
non-default settings.
Is this supposed to happen? How can i prevent these kind of numbers?
Thanks,
Markus
19 matches
Mail list logo
