You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2018/07/09 11:05:00 UTC
[jira] [Updated] (LUCENE-8392) TieredMergePolicy has broken
assumptions when maxMergeAtOnce is greater than segmentsPerTier
[ https://issues.apache.org/jira/browse/LUCENE-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand updated LUCENE-8392:
---------------------------------
Attachment: LUCENE-8392.patch
> TieredMergePolicy has broken assumptions when maxMergeAtOnce is greater than segmentsPerTier
> --------------------------------------------------------------------------------------------
>
> Key: LUCENE-8392
> URL: https://issues.apache.org/jira/browse/LUCENE-8392
> Project: Lucene - Core
> Issue Type: Test
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-8392.patch
>
>
> While working on LUCENE-8391 I had test failures when {{maxMergeAtOnce}} is larger than {{segmentsPerTier}}. For instance when all segments are on the same tier, the maximum number of segments that is allowed in the index is {{segmentsPerTier}} but because the tiered policy wants to find {{maxMergeAtOnce}} segments to merge, no segments will get merged if there are less than {{maxMergeAtOnce}} segments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org