[ https://issues.apache.org/jira/browse/LUCENE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Willnauer resolved LUCENE-9339. ------------------------------------- Fix Version/s: 8.6 master (9.0) Lucene Fields: New,Patch Available (was: New) Assignee: Simon Willnauer Resolution: Fixed > Only call MergeScheduler when we actually found new merges > ---------------------------------------------------------- > > Key: LUCENE-9339 > URL: https://issues.apache.org/jira/browse/LUCENE-9339 > Project: Lucene - Core > Issue Type: Improvement > Affects Versions: master (9.0), 8.6 > Reporter: Simon Willnauer > Assignee: Simon Willnauer > Priority: Major > Fix For: master (9.0), 8.6 > > Time Spent: 20m > Remaining Estimate: 0h > > IW#maybeMerge calls the MergeScheduler even if it didn't find any merges we > should instead only do this if there is in-fact anything there to merge and > safe the call into a sync'd method. In addition to this we never respect the > _newMergesFound_ parameter. It seems unnecessary and can be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org