lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Rutherglen <jason.rutherg...@gmail.com>
Subject Re: NRT getReader turnaround on large segments
Date Thu, 28 May 2009 19:46:54 GMT
Also important to note that only with ConcurrentMergeScheduler will the
segmentReader warming occur in the background.  When using
SerialMergeScheduler, the warming will happen in the foreground.

On Thu, May 28, 2009 at 12:40 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> Right.  If you play w/ this please report back on how it goes!
>
> Mike
>
> On Thu, May 28, 2009 at 3:38 PM, Jason Rutherglen
> <jason.rutherglen@gmail.com> wrote:
> > And warming a segment in mergeMiddle doesn't block the addition of new
> > segments.
> >
> > On Thu, May 28, 2009 at 12:30 PM, Michael McCandless
> > <lucene@mikemccandless.com> wrote:
> >>
> >> This is exactly why we added IndexReaderWarmer -- it pre-warms a newly
> >> merged segment before committing to SegmentInfos.
> >>
> >> So, while such warming is happening, if getReader() is called, the
> >> returned reader will still read the old segments.
> >>
> >> Mike
> >>
> >> On Thu, May 28, 2009 at 3:06 PM, Jason Rutherglen
> >> <jason.rutherglen@gmail.com> wrote:
> >> > An interesting discussion came up.  How do we handle IW.getReader
> >> > turnaround
> >> > time on large new segments?
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-dev-help@lucene.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>

Mime
View raw message