[#LUCENE-1210] IndexWriter & ConcurrentMergeScheduler deadlock case if starting a merge hits an exception - ASF JIRA

Issue Details (XML | Word | Printable)

Key:	LUCENE-1210
Type:	Bug
Status:	Closed
Resolution:	Fixed
Priority:	Minor
Assignee:	Michael McCandless
Reporter:	Michael McCandless
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Lucene - Java

IndexWriter & ConcurrentMergeScheduler deadlock case if starting a merge hits an exception

Created: 09/Mar/08 08:05 AM Updated: 08/May/08 07:47 PM

Return to search

Component/s:

Index

Affects Version/s:

2.3, 2.3.1

Fix Version/s:

2.3.2, 2.4

Time Tracking:

Not Specified

Lucene Fields:	New
Resolution Date:	09/Mar/08 08:18 AM

Description

If you're using CMS (the default) and mergeInit hits an exception (eg
OOME), we are not properly clearing IndexWriter's internal tracking of
running merges. This causes IW.close() to hang while it incorrectly
waits for these non-started merges to finish.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Michael McCandless added a comment - 09/Mar/08 08:06 AM

The fix is trivial: add a try/finally to mergeInit to clear the
internal tracking on exception. I'll commit shortly.

[ Permlink | « Hide ]

Michele Bini added a comment - 10/Mar/08 10:08 AM

Uhm, shouldn't the patch be committed in the 2.3 branch, too, as it affects 2.3.1?

[ Permlink | « Hide ]

Michael McCandless added a comment - 10/Mar/08 10:13 AM

Yes, I agree. At some point soon we should do a 2.3.2 point release, and I'll port this issue back for that.

[ Permlink | « Hide ]

Hoss Man added a comment - 11/Mar/08 07:29 PM

targeted for 2.3.2 bug fix release