[ https://issues.apache.org/jira/browse/LUCENE-9339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089969#comment-17089969 ]
ASF subversion and git services commented on LUCENE-9339: --------------------------------------------------------- Commit 4a98918bfa2d57d35ac12c5d49e8f04fcd9791ae in lucene-solr's branch refs/heads/master from Simon Willnauer [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=4a98918 ] LUCENE-9339: Only call MergeScheduler when we actually found new merges (#1445) 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. > 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 > Priority: Major > 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