[LUCENE-2324] Per thread DocumentsWriters that write their own private segments

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Realtime Branch
• Component/s: core/index
• Lucene Fields: New
• Assignee: Michael Busch
• Reporter: Michael Busch
• Created: 15/Mar/10 05:40
• Updated: 28/Aug/22 12:22
• Resolved: 28/Apr/11 15:19

Description

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.

Issue Links

• blocks: LUCENE-2312 Search on IndexWriter's RAM Buffer
• is blocked by: LUCENE-3028 IW.getReader() returns inconsistent reader on RT Branch
• is blocked by: LUCENE-2956 Support updateDocument() with DWPTs
• is blocked by: LUCENE-2881 Track FieldInfo per segment instead of per-IW-session
• is related to: LUCENE-2293 IndexWriter has hard limit on max concurrency
• relates to: LUCENE-2573 Tiered flushing of DWPTs by RAM with low/high water marks