lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Earwin Burrfoot (JIRA)" <>
Subject [jira] Commented: (LUCENE-2485) IndexWriter should also warm flushed segments
Date Wed, 02 Jun 2010 16:40:39 GMT


Earwin Burrfoot commented on LUCENE-2485:

bq. As long as warming a new segment doesn't block that new segment from being exposed via
If an application needs warming, it will need to warm up new segments exposed through getReader()
anyway. If you're bent on fast turnaround, you're probably not relying on things being warmed
up (or okay with the costs).
Add to this the thing that for realtime-hungry deployments the size of newly-created (not
merged) segments is likely smallish, and any warmup (if present) will take negligible time.

I think you're going to do a bit of overoptimizing here.

> IndexWriter should also warm flushed segments
> ---------------------------------------------
>                 Key: LUCENE-2485
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael McCandless
>             Fix For: 4.0
> Spinoff of LUCENE-2311.
> You can now set a mergedSegmentWarmer on IW, which warms only newly merged segments.
> But for consistency maybe we should change this to warm all new segments (ie, also flushed
ones).  We should rename it to something "setSegmentWarmer".
> Really, the reader pool should be pulled out of IndexWriter, be externally provided,
and be responsible for doing warming of new segments.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message