[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981830#action_12981830
]
Jason Rutherglen commented on LUCENE-2324:
------------------------------------------
Also multiple threads can call DocumentsWriterPerThread.addDocument and that's
resulting in this:
{code}[junit] java.lang.AssertionError: omitTermFreqAndPositions:false
postings.docFreqs[termID]:0
[junit] at
org.apache.lucene.index.FreqProxTermsWriterPerField.addTerm(FreqProxTermsWriterPerField.java:143)
[junit] at
org.apache.lucene.index.TermsHashPerField.add(TermsHashPerField.java:234)
[junit] at
org.apache.lucene.index.DocInverterPerField.processFields(DocInverterPerField.java:91)
[junit] at
org.apache.lucene.index.DocFieldProcessor.processDocument(DocFieldProcessor.java:274)
[junit] at
org.apache.lucene.index.DocumentsWriterPerThread.addDocument(DocumentsWriterPerThread.java:184)
[junit] at
org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:374)
[junit] at
org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1403)
[junit] at
org.apache.lucene.index.IndexWriter.updateDocument(IndexWriter.java:1375)
{code}
> Per thread DocumentsWriters that write their own private segments
> -----------------------------------------------------------------
>
> Key: LUCENE-2324
> URL: https://issues.apache.org/jira/browse/LUCENE-2324
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: Realtime Branch
>
> Attachments: LUCENE-2324-SMALL.patch, LUCENE-2324-SMALL.patch,
> LUCENE-2324-SMALL.patch, LUCENE-2324-SMALL.patch, LUCENE-2324-SMALL.patch,
> lucene-2324.patch, lucene-2324.patch, LUCENE-2324.patch, test.out, test.out,
> test.out
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
