[ 
https://issues.apache.org/jira/browse/LUCENE-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538168#comment-16538168
 ] 

ASF subversion and git services commented on LUCENE-8393:
---------------------------------------------------------

Commit 97833b729e310a8cd4a1ba5a8e0e132927a82699 in lucene-solr's branch 
refs/heads/branch_7x from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=97833b7 ]

LUCENE-8393: TieredMergePolicy needs to take into account the maximum segment 
size when computing the allowed number of segments.


> TieredMergePolicy needs to take into account the maximum segment size when 
> computing the allowed number of segments
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-8393
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8393
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Priority: Minor
>         Attachments: LUCENE-8393.patch
>
>
> This is a pre-existing issue that was made more likely by LUCENE-7976, given 
> that segments that are larger than the max segment size divided by 2 now are 
> potential candidates for merging: when computing the allowed number of 
> segments, TieredMergePolicy multiplies the level size by {{maxMergeAtOnce}} 
> until it finds a level that isn't full. It currently assumes that the level 
> size is always less than the maximum segment size, which might not always be 
> true. This might lead to underestimating the allowed number of segments and 
> in-turn causing excessive merging.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to