You don't have to worry about background merges when optimizing, it
won't error out.

Optimize is a little heavy handed though.

You might just use expunge deletes and/or try a low merge factor -
though with the latest tiered merge policy, I think you have to use a
different knob than merge factor that I don't know offhand...

Mark

On Wed, Sep 19, 2012 at 4:16 PM, roz dev <rozde...@gmail.com> wrote:
> Hi All
>
> I need input from community about the idea of doing explicit optimization
> of Solr Index and benefit/negatives of doing this.
>
> I know that Background merge also happens and am wondering if background
> merge is going on and then i trigger explicit commit then will it error out?
>
> How do these 2 things work together?
>
> What is the preferred way to keep the index size smaller, in terms of
> number of documents. In my case, I want to keep the max doc to low number
> so that
> memory cost of field cache is not too high.
>
> Any thoughts?
>
> -Saroj



-- 
- Mark

Reply via email to