You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2022/05/23 14:31:00 UTC
[jira] [Commented] (LUCENE-10078) Enable merge-on-refresh by default?
[ https://issues.apache.org/jira/browse/LUCENE-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540979#comment-17540979 ]
Adrien Grand commented on LUCENE-10078:
---------------------------------------
We had discussions about this in the context of the O(n^2) merging that {{floorSegmentSize}} introduces (LUCENE-10574), so I took a stab at this issue, so that users fully benefit from the trade-off we're making of creating unbalanced merges for the sake of having fewer segments to deal with at search time.
> Enable merge-on-refresh by default?
> -----------------------------------
>
> Key: LUCENE-10078
> URL: https://issues.apache.org/jira/browse/LUCENE-10078
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is a spinoff from the discussion in LUCENE-10073.
> The newish merge-on-refresh ([crazy origin story|https://blog.mikemccandless.com/2021/03/open-source-collaboration-or-how-we.html]) feature is a powerful way to reduce searched segment counts, especially helpful for applications using many indexing threads. Such usage will write many tiny segments on each refresh, which could quickly be merged up during the {{refresh}} operation.
> We would have to implement a default for {{findFullFlushMerges}} (LUCENE-10064 is open for this), and then we would need {{IndexWriterConfig.getMaxFullFlushMergeWaitMillis}} a non-zero value (this issue).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org