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 < [email protected]> 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 > <[email protected]> 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 > > <[email protected]> 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 > >> <[email protected]> wrote: > >> > An interesting discussion came up. How do we handle IW.getReader > >> > turnaround > >> > time on large new segments? > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
