> Uwe Schindler wrote:
> TieredMP is already the default in Lucene 3.5, unless you explicitely set
> another one!
>
I was going to add the detail that I was running 3.4 at the moment (I'm looking
to upgrade very soon) and thought
LogByteSizeMergePolicy was the default there, but I am wrong th
Hi,
> Interesting coincidence, just last night one of our in-house indexes must
have
> decide it could use some merging and dropped 5 segments (of ~30+) and 4-5
> GB (of a total ~20-25 GB). So it was great to see it in action.
>
> I'm in no hurry, but I'll be eventually looking into using
TieredM
> I think a good question is whether you are really seeing performance issues
> due to the 1/3 deleted-
> but-not-yet-reclaimed documents...
No, I'm NOT worried about performance. I've got the message about optimize().
I was just looking for something I might do maybe once or twice a year when
Maybe try TieredMergePolicy to see if it'd do any merges here...?
More responses below:
On Tue, Mar 6, 2012 at 8:00 PM, Paul Hill wrote:
> I have an index with 421163 documents (including body text)
> after running a test index for a couple of months with 3.4 code with the
> default LogByteSiz
I'm running with 3.4 code and have studied up on all the API related to the
optimize() replacements and understand I needn't worry about deleted documents,
but I still want to ask a few things about keeping the index in good shape
And about merge policy.
I have an index with 421163 documents (in
