[LUCENE-1611] Do not launch new merges if IndexWriter has hit OOME

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.9
• Component/s: core/index
• Lucene Fields: New
• Assignee: Michael McCandless
• Reporter: Michael McCandless
• Created: 24/Apr/09 21:37
• Updated: 28/Aug/22 11:59
• Resolved: 30/Apr/09 19:58

Description

if IndexWriter has hit OOME, it defends itself by refusing to commit changes to the index, including merges. But this can lead to infinite merge attempts because we fail to prevent starting a merge.

Spinoff from http://www.nabble.com/semi-infinite-loop-during-merging-td23036156.html.