Started by upstream project "Lucene-main-Linux" build number 68,31868318Lucene-main-Linuxjob/Lucene-main-Linux/22e5c8f72f00f5348beb8d8ef197b44c2314d27430e5c8f72f00f5348beb8d8ef197b44c2314d27430refs/remotes/origin/branch_11xe5c8f72f00f5348beb8d8ef197b44c2314d27430e5c8f72f00f5348beb8d8ef197b44c2314d27430refs/remotes/origin/branch_11xe5c8f72f00f5348beb8d8ef197b44c2314d27430e5c8f72f00f5348beb8d8ef197b44c2314d27430refs/remotes/origin/branch_11xhttps://gitbox.apache.org/repos/asf/lucene.git078719279testReportfalseJava: 64bit/hotspot/jdk-26.0.1 -XX:+UseCompressedOops -XX:+UseG1GC#22891039891039Lucene-11.x-Linux #2222falsefalse22238888SUCCESS1793357366912https://jenkins.thetaphi.de/view/Lucene/job/Lucene-11.x-Linux/22/lucene/core/src/java/org/apache/lucene/index/DocumentsWriterFlushControl.javalucene/CHANGES.txtlucene/core/src/java/org/apache/lucene/index/FlushByRamOrCountsPolicy.javalucene/core/src/test/org/apache/lucene/index/TestIndexWriterDelete.javacdfe8aa782936c0455fcc3a8232ac217bdec259b1793356014000https://jenkins.thetaphi.de/user/romseygeekromseygeekromseygeek@apache.orgAvoid overflows in IndexWriter's delete buffer (#16867) The delete queue for IndexWriter is shared between all indexing threads, and holds a ByteBlockPool that tracks all terms being used for delete queries. While the individual indexing threads have their own maximum buffer size of 1945Mb to avoid overflowing any internal data structures, it is possible for this shared buffer to overflow if multiple threads are adding to it, and a particularly slow flush prevents it from being cleared. This adds a specific limit to the delete buffer (at the same size as the limits in DocumentsWriterPerThread), and also wires it into stall control so that other threads don't prevent the buffer being flushed once it hits the limit. 2026-10-30 10:26:54 +0000cdfe8aa782936c0455fcc3a8232ac217bdec259bAvoid overflows in IndexWriter's delete buffer (#16867)editlucene/core/src/java/org/apache/lucene/index/FlushByRamOrCountsPolicy.javaeditlucene/CHANGES.txteditlucene/core/src/java/org/apache/lucene/index/DocumentsWriterFlushControl.javaeditlucene/core/src/test/org/apache/lucene/index/TestIndexWriterDelete.javalucene/core/src/java/org/apache/lucene/search/FieldValueHitQueue.javalucene/core/src/test/org/apache/lucene/search/TestTopFieldCollectorEarlyTermination.javalucene/CHANGES.txte5c8f72f00f5348beb8d8ef197b44c2314d274301793356704000https://jenkins.thetaphi.de/user/romseygeekromseygeekromseygeek@apache.orgDisable sort-based early termination for indexes with document blocks (#16947) When an index defines a parent-child structure using IndexWriterConfig# setParentField, index sorting only looks at field values on parent documents. This means that sort-based early termination cannot use the value of its latest document as a cut-off, because it could be from a child document and later parent documents would be competitive. This commit disables sort-based early termination for indexes marked this way. Field-based pruning via competitive iterators continues to work as normal. 2026-10-30 10:38:24 +0000e5c8f72f00f5348beb8d8ef197b44c2314d27430Disable sort-based early termination for indexes with document blocks (#16947)editlucene/CHANGES.txteditlucene/core/src/java/org/apache/lucene/search/FieldValueHitQueue.javaeditlucene/core/src/test/org/apache/lucene/search/TestTopFieldCollectorEarlyTermination.javagithttps://jenkins.thetaphi.de/user/romseygeekromseygeek