lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <>
Subject [jira] Updated: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments
Date Fri, 26 Mar 2010 21:34:27 GMT


Jason Rutherglen updated LUCENE-2324:

    Attachment: LUCENE-2324.patch

The patch is not committable.  

The basics are here.  We can worry about max threads later.  For now there's a doc writer
per thread.  I still don't fully understand remap deletes, so it's commented out.  There's
a flushedDocCount per DW, and a global one in IW.  

IWC is accessed directly where possible.

When running TestIndexWriter, the DW resumeAllThreads assertion fails.

If the total ram buffer size is too large, and the current thread's DW is the largest, it's
flushed.  The next test case can be in regards to the memory management.  

> Per thread DocumentsWriters that write their own private segments
> -----------------------------------------------------------------
>                 Key: LUCENE-2324
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael Busch
>            Assignee: Michael Busch
>            Priority: Minor
>             Fix For: 3.1
>         Attachments: LUCENE-2324.patch
> See LUCENE-2293 for motivation and more details.
> I'm copying here Mike's summary he posted on 2293:
> Change the approach for how we buffer in RAM to a more isolated
> approach, whereby IW has N fully independent RAM segments
> in-process and when a doc needs to be indexed it's added to one of
> them. Each segment would also write its own doc stores and
> "normal" segment merging (not the inefficient merge we now do on
> flush) would merge them. This should be a good simplification in
> the chain (eg maybe we can remove the *PerThread classes). The
> segments can flush independently, letting us make much better
> concurrent use of IO & CPU.

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