[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated LUCENE-2324:
-------------------------------------
Attachment: LUCENE-2324-SMALL.patch
I added a FlushPolicy class, deletes record the ram used to DWPT and DW.
Recording to DW is for global ram used. The TIW OOM is still occurring
however. The delete calls to FlushControl are gone, I'm not sure what's going
to be left of it.
bq. I'm not sure we should queue. I wonder how much this'd slow down the single
threaded case?
Yes, that's a good point.
bq. We shouldn't do global waiting anymore - this is what's great about DWPT.
However we'll have global waiting for the flush all threads case. I think that
can move down to DW though. Or should it simply be a sync in/on IW?
bq. I thought we don't have sequence IDs anymore?
The seqid lock was there, however it was removed in the last update. I think
we need to clearly document the various locks and sync points as right now it's
not clear enough to prevent deadlock situations.
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
