: HTTP, I tried to optimize by passing the true flag to the : CommitUpdateCommand. : : When optimizing an index with Lucene directly it doubles the size of the : index temporarily and then deletes the old segments that were optimized. : Instead, what happened was the old segments were still there. Calling : optimize a second time did remove the old segments.
you explicitly mentioned EmbeddedSolr -- are you seeing different behavior if you run Solr in a servlet container? are you by any chance running on a windows platform? I suspect that you are and this is the normal behavior because there is an open IndexReader so the optimize command can't remove the old files. once the optimize is finished, the new reader is opened and the old reader is closed, then the next optimize command can cleanly remove the old files. -Hoss
