Do you have a reader open on the index which was opened before your
your index was optimized? Maybe there is a reader around holding on
the references to the merged segments.

simon

On Thu, Jan 7, 2010 at 5:23 PM, Yuliya Palchaninava <y...@solute.de> wrote:
> Hi,
>
> According to the api documentation: "In general, once the optimize completes, 
> the total size of the index will be less than the size of the starting index. 
> It could be quite a bit smaller (if there were many pending deletes) or just 
> slightly smaller". In our case the index becomes not smaller but larger, 
> namely thrice as large.
>
> The not optimized index doesn't contain compressed fields, what could have 
> caused the growth of the index due to the otimization. So we cannot explain 
> what happens.
>
> Does someone have an explanation for the index growth due to the optimization?
>
> Thanks,
> Yuliya
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Reply via email to