lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr
Date Wed, 06 Jan 2016 23:17:40 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086474#comment-15086474
] 

Jack Krupansky commented on SOLR-3141:
--------------------------------------

bq. optimize() is rarely necessary anymore

Well... I used to say that same thing, because I was under the impression that the common
merge policies would automatically optimize segments over time, but over the past year there
have been several email threads with users who had heavy update/delete usage patterns where
the index size appeared to remain bloated due to deleted/updated documents.

So... we need a revised story... and doc.

What exactly should we be telling people who update/delete lots of docs frequently and still
find that the index is bloated?

Is there maybe some underlying bug or tuning of the delete/merge policy needed?

Or... maybe people still need an explicit "force merge" command to effectively say "I just
finished a large batch of document updates/deletes but I'm done now, so merge away."

Personally, I would like to see a "start batch" mode, which signals that the user intends
to make a lot of changes and Solr/Lucene should make no attempt to optimize or clean things
up or update caches until the user signals "end of batch", at which time any appropriate merging
or optimization or cache refreshing can occur. Not everybody will want to do this, but it
still seems to be a semi-common use of Solr.


> Deprecate OPTIMIZE command in Solr
> ----------------------------------
>
>                 Key: SOLR-3141
>                 URL: https://issues.apache.org/jira/browse/SOLR-3141
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 3.5
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>              Labels: force, optimize
>             Fix For: 4.9, Trunk
>
>         Attachments: SOLR-3141.patch, 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message