You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2015/08/07 13:38:45 UTC
[jira] [Commented] (SOLR-1560) make "optimize" do partial optimizes
under the covers
[ https://issues.apache.org/jira/browse/SOLR-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661693#comment-14661693 ]
Jan Høydahl commented on SOLR-1560:
-----------------------------------
Still relevant?
> make "optimize" do partial optimizes under the covers
> -----------------------------------------------------
>
> Key: SOLR-1560
> URL: https://issues.apache.org/jira/browse/SOLR-1560
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Hoss Man
>
> In Lucene, an optimize() call iteratively merges segments until only one is left - and while it's merging it (ultimately) needs to make a copy of the entire index, because readers attempting to open the index "mid-optimize" need to see a consistent copy of the index.
> In Solr, we have control over when new readers/searchers get opened, so what if when we recieved an <optimize/> command, we under the covers we made iterative partial optimize calls and only opened a new searcher when we were finished with all of them? In theory this seems like it would help reduce the disk space used during optimize, without really affecting the time it takes to "optimize"
> These are the threads that prompted this idea...
> http://old.nabble.com/eternal-optimize-interrupted-to24805680.html#a24805680
> http://old.nabble.com/Re%3A-eternal-optimize-interrupted-to24928754.html#a24928754
> http://old.nabble.com/Optimization-of-large-shard-succeeded-to25809281.html#a25809281
--
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