There are a few bugs for which you require to merge the index, see SOLR-8807
and related bugs.
https://issues.apache.org/jira/browse/SOLR-8807
-Original message-
> From:Erick Erickson
> Sent: Wednesday 3rd October 2018 4:50
> To: solr-user
> Subject: Re: Opinions on index
The problem you're at now is that, having run optimize, that single
massive segment will accumulate deletes until it has < 2.5G "live"
documents. So once you do optimize (and until you get to Solr 7.5),
unless you can live with this one segment accumulating deletes for a
very long time, you must co
Don’t optimize. The first article isn’t as clear as it should be. The important
sentence is "Unless you are running into resource problems, it’s best to leave
merging alone.”
I’ve been running Solr in production since version 1.3, with several different
kinds and sizes of collections. I’ve neve
We run an old master/slave solr 4.3.0 solr cluster
14 nodes 7/7
indexes average 47/5 gig per shard around 2 mill docs per shard.
We have constant daily additions and a small amount of deletes.
We optimize nightly currently and it is a system hog.
Is it feasible to never run optimize?
I ask bec
