[
https://issues.apache.org/jira/browse/LUCENE-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071760#comment-16071760
]
ASF subversion and git services commented on LUCENE-7894:
---------------------------------------------------------
Commit ee1edd9d467bbccfe7015ec5ebee93f8b5bd4b14 in lucene-solr's branch
refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ee1edd9 ]
LUCENE-7894: make sure IW finishes segment flush so we don't see a temporary
drop in IW.maxDoc()
> IndexWriter suffers temporary short-term amnesia
> ------------------------------------------------
>
> Key: LUCENE-7894
> URL: https://issues.apache.org/jira/browse/LUCENE-7894
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Blocker
> Fix For: master (7.0)
>
> Attachments: LUCENE-7894.patch
>
>
> Nightly benchmarks had been failing to run for a while due to trunk API
> changes, but when I finally fixed those, the indexer fails because
> {{IW.maxDoc}} disagrees with the number of documents indexed after all
> threads are done indexing.
> It's sort of crazy none of our tests caught this!
> I tracked down the bug; it was caused in LUCENE-7868. The bug is not as bad
> as it sounds: documents are not in fact lost, it's just IW's internal
> accounting for maxDoc that's temporarily incorrect until you do a refresh or
> commit or close the index.
> I'm marking as blocker for 7.0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
