You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/06/22 00:00:00 UTC
[jira] [Resolved] (LUCENE-8965) ConcurrentMergeScheduler should
maybe sometimes do synchronously
[ https://issues.apache.org/jira/browse/LUCENE-8965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved LUCENE-8965.
----------------------------------
Resolution: Won't Fix
Obsoleted by LUCENE-8962
> ConcurrentMergeScheduler should maybe sometimes do synchronously
> ----------------------------------------------------------------
>
> Key: LUCENE-8965
> URL: https://issues.apache.org/jira/browse/LUCENE-8965
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> It can be beneficial for the ConcurrentMergeScheduler to sometimes _not_ do concurrent merges (i.e. sometimes do a serial merge). When the provided "OneMerge" is _small_ and when the MergeTrigger is FULL_FLUSH (i.e. on a commit), a new searcher would benefit from seeing fewer segments. If index replication is used, this setting can reduce the net replication by merging a little more eagerly sometimes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org