[
https://issues.apache.org/jira/browse/LUCENE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412971#comment-17412971
]
Adrien Grand commented on LUCENE-10088:
---------------------------------------
+1 to this one-line fix to avoid worst-case scenarios
bq. OOM would be another
+1 More generally I dislike that IndexWriter may use much more memory than
configured on the IndexWriterConfig. Is there a way that blocked flushes could
still be accounted against maxBufferedDocs/ramBufferSizeMB, and that
IndexWriter would stall indexing when blocked flushes consume the entire
maxBufferedDocs/ramBufferSizeMB budget?
> Too many open files in
> TestIndexWriterMergePolicy.testStressUpdateSameDocumentWithMergeOnGetReader
> --------------------------------------------------------------------------------------------------
>
> Key: LUCENE-10088
> URL: https://issues.apache.org/jira/browse/LUCENE-10088
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Priority: Major
>
> [This build
> failure|https://ci-builds.apache.org/job/Lucene/job/Lucene-NightlyTests-main/386/]
> reproduces for me. I'll try to dig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
