lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8043) Attempting to add documents past limit can corrupt index
Date Fri, 01 Dec 2017 16:43:00 GMT


Michael McCandless commented on LUCENE-8043:

Thanks [~simonw]; I love the new assert, and the patch looks correct to me.

I beasted all Lucene tests 33 times and hit this failure, twice:

ant test -Dtestcase=TestIndexWriter -Dtestmethod=testThreadInterruptDeadlock -Dtests.seed=55197CA38E8C827B

java.lang.AssertionError: pendingNumDocs 0 != 11 totalMaxDoc
        at org.apache.lucene.index.IndexWriter.shutdown(
        at org.apache.lucene.index.IndexWriter.close(
        at org.apache.lucene.index.TestIndexWriter$

But it does not reproduce for me.

I hit two other unrelated failures; look like Similarity issues ... I'll open separate issues
for those.

> Attempting to add documents past limit can corrupt index
> --------------------------------------------------------
>                 Key: LUCENE-8043
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.10, 7.0, master (8.0)
>            Reporter: Yonik Seeley
>            Assignee: Simon Willnauer
>             Fix For: master (8.0), 7.2, 7.1.1
>         Attachments: LUCENE-8043.patch, LUCENE-8043.patch, LUCENE-8043.patch, LUCENE-8043.patch,
> The IndexWriter check for too many documents does not always work, resulting in going
over the limit.  Once this happens, Lucene refuses to open the index and throws a CorruptIndexException:
Too many documents.
> This appears to affect all versions of Lucene/Solr (the check was first implemented in
LUCENE-5843 in v4.9.1/4.10 and we've seen this manifest in 4.10) 

This message was sent by Atlassian JIRA

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

View raw message