lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4080) SegmentReader.numDeletedDocs() sometimes gives an incorrect numDeletedDocs
Date Fri, 29 Jun 2012 12:21:44 GMT


Adrien Grand updated LUCENE-4080:

    Attachment: LUCENE-4080.patch

New patch (simpler than the previous ones). This time, I only removed {{MergeState.IndexReaderAndLiveDocs}}
and modified {{IndexWriter.mergeMiddle}} so that it fixes the merge reader in case its del
count doesn't match the {{ReadersAndLiveDocs}} del count. There shouldn't be more contention
as with the current trunk version.
> SegmentReader.numDeletedDocs() sometimes gives an incorrect numDeletedDocs
> --------------------------------------------------------------------------
>                 Key: LUCENE-4080
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.0, 4.1
>            Reporter: Adrien Grand
>            Priority: Trivial
>             Fix For: 4.1
>         Attachments: LUCENE-4080.patch, LUCENE-4080.patch, LUCENE-4080.patch
> At merge time, SegmentReader sometimes gives an incorrect value for numDeletedDocs.
> From LUCENE-2357:
> bq. As far as I know, [SegmenterReader.numDeletedDocs() is] only unreliable in this context
(SegmentReader passed to SegmentMerger for merging); this is because we allow newly marked
deleted docs to happen concurrently up until the moment we need to pass the SR instance to
the merger (search for "// Must sync to ensure BufferedDeletesStream" in
... but it would be nice to fix that, so I think open a new issue (it won't block this one)?
We should be able to make a new SR instance, sharing the same core as the current one but
using the correct delCount...
> bq. It would be cleaner (but I think hairier) to create a new SR for merging that holds
the correct delCount, but let's do that under the separate issue.
> bq.  it would be best if the SegmentReader's numDeletedDocs were always correct, but,
fixing that in IndexWriter is somewhat tricky. Ie, the fix could be hairy but the end result
("SegmentReader.numDeletedDocs can always be trusted") would be cleaner...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message