[
https://issues.apache.org/jira/browse/SOLR-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Rafalovitch closed SOLR-1560.
---------------------------------------
Resolution: Not A Problem
Nobody confirmed if this still relevant in more than a year. I suspect it is
not with a lot of changes since this issue was opened.
> 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: [email protected]
For additional commands, e-mail: [email protected]
