Marvin Humphrey <mar...@rectangular.com> wrote: > 4) Allow 2 concurrent writers: one for small, fast updates, and one for > big background merges.
Marvin can you describe more detail here? It sounds like this is your solution for "decoupling" segments changes due to merges from changes from docs being indexed, from a reader's standpoint? Since you are using mmap to achieve near zero brand-new IndexReader creation, whereas in Lucene we are moving towards achieving real-time by always reopening a current IndexReader (not a brand new one), it seems like you should not actually have to worry about the case of reopening a reader after a large merge has finished? We need to deal with this case (background the warming) because creating that new SegmentReader (on the newly merged segment) can take a non-trivial amount of time. Mike
