jpountz commented on PR #14232:
URL: https://github.com/apache/lucene/pull/14232#issuecomment-2657233927
Thanks for looking into this and sorry for missing the build failures. The
fact that this test has failures makes sense to me since merging is a bit more
aggressive now, though I don't expect it to be a problem in practice. Another
way of making the number of clones more predictable would be to avoid merges
below the floor size, ie.
```patch
diff --git
a/lucene/core/src/test/org/apache/lucene/index/TestForTooMuchCloning.java
b/lucene/core/src/test/org/apache/lucene/index/TestForTooMuchCloning.java
index 92470083540..4834ad9219f 100644
--- a/lucene/core/src/test/org/apache/lucene/index/TestForTooMuchCloning.java
+++ b/lucene/core/src/test/org/apache/lucene/index/TestForTooMuchCloning.java
@@ -37,6 +37,7 @@ public class TestForTooMuchCloning extends LuceneTestCase {
final MockDirectoryWrapper dir = newMockDirectory();
final TieredMergePolicy tmp = new TieredMergePolicy();
tmp.setSegmentsPerTier(2);
+ // Disable merges below the floor size, which are otherwise allowed to
merge more than segmentsPerTier segments together
+ tmp.setFloorSegmentMB(Double.MIN_VALUE);
final RandomIndexWriter w =
new RandomIndexWriter(
random(),
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
