All,
Solr 5.4 with emdbedded Jetty (4G heap)
Trying to understand behavior of "optimize" operation if not run
explicitly. What is the frequency at which this operation is run, what
are the storage requirements and how do we schedule it? Any
comments/pointers would greatly help.
Thanks in ad
Thanks Erick. This helps.
On 3/16/16 10:11 AM, Erick Erickson wrote:
First of all, "optimize-like" does _not_ happen
"every time a commit happens". What _does_ happen
is the current state of the index is examined and if
certain conditions are met _then_ segment
merges happen. Think of these as "
In general, don't bother with optimize unless the index is quite static,
i.e. there are very few adds/updates or those updates are done in
batches and rarely (i.e. once a day or less frequently).
As far as space, this will require that you have at _least_ as much
free space on your disks as your i
Erick, Thanks for the response. Comments in line...
On 3/16/16 9:56 AM, Erick Erickson wrote:
In general, don't bother with optimize unless the index is quite static,
i.e. there are very few adds/updates or those updates are done in
batches and rarely (i.e. once a day or less frequently).
As fa
First of all, "optimize-like" does _not_ happen
"every time a commit happens". What _does_ happen
is the current state of the index is examined and if
certain conditions are met _then_ segment
merges happen. Think of these as "partial optimizes".
This is under control of the TieredMergePolicy by
d
