lucene-dev mailing list archives

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


Jason Rutherglen commented on LUCENE-2324:

Currently the doc writer manages the ram buffer size, however
this needs to be implemented across doc writers for this issue
to be complete. IW addDoc returns doFlush from DW. I don't think
doFlush will be useful anymore?

A slightly different memory management needs to be designed.
Right now we allow the user to set the max ram buffer size and
when the doc writer's buffers exceed the ram limit, the buffer
is flushed and the process is complete.

With this issue, the flush logic probably needs to be bumped up
into IW, and flushing becomes a multi-docwriter ram usage
examination. For starters, if the aggregate ram usage of all doc
writers exceeds the IWC defined ram buffer size, we need to
schedule flushing the doc writer with the greatest ram usage? I
wonder if there's something I'm missing here in regards to
synchronization issues with DW?

> 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
> 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