lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Sun, 19 Feb 2012 23:52:34 GMT


Yonik Seeley commented on SOLR-3141:

Creative use of google, but it does't always add up.  Just looking randomly at a couple:

The vufind reference oddly states that you should optimize after updating, but it also states:
bq. Note: Optimizing the index can take a lot of server resources, so you should schedule
your index updates and optimizations for non-peak times when possible.
So you can see they have that very infrequent update model in mind, and they seem well aware
of the cost of an optimize.

The stackoverflow is a thing asking how to automate commit and optimize and how often he should

And the archiveorange link mentions a guy optimizing, but it's certainly not clear at all
that he shouldn't be....  we don't know his requirements.

Solr is at 400 downloads a day via the website (twice that many visit the download page...
but the actual link is hard to see!).  Yes, I'll stand by "minority".
> Deprecate OPTIMIZE command in Solr
> ----------------------------------
>                 Key: SOLR-3141
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 3.5
>            Reporter: Jan H√łydahl
>              Labels: force, optimize
>             Fix For: 3.6
>         Attachments: SOLR-3141.patch, SOLR-3141.patch
> Background: LUCENE-3454 renames optimize() as forceMerge(). Please read that issue first.
> Now that optimize() is rarely necessary anymore, and renamed in Lucene APIs, what should
be done with Solr's ancient optimize command?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message