[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981519#action_12981519
]
Jason Rutherglen commented on LUCENE-2324:
------------------------------------------
bq. look at ThreadAffinityDocumentsWriterThreadPool. There I'm able to use
things like tryLock() and getQueueLength().
Makes sense, I had only read the DocumentsWriterPerThreadPool part.
* DWPT.perDocAllocator and freeLevel can be removed?
* DWPT's RecyclingByteBlockAllocator -> DirectAllocator?
* Looks like the deletes handling is updated to the patch
* I don't think we need FlushControl anymore as the RAM tracking should occur
in DW and there's no need for IW to [globally] wait for flushes.
* The locking is more clear now, I can see DW.updateDocument locks the
threadstate as does flushAllThreads.
I'll reincorporate the RAM tracking, and then will try the unit tests again.
I'm curious if the file not found errors are gone.
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
