[LUCENE-3627] CorruptIndexException on indexing after a failure occurs after segments file creation but before any bytes are written

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.5
• Fix Version/s: 3.6, 4.0-ALPHA

Environment

lucene-3.5.0, src download from GA release lucene.apache.org.
Mac OS X 10.6.5, running tests in Eclipse Build id: 20100218-1602,
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode)

• Lucene Fields: New, Patch Available
• Assignee: Michael McCandless
• Reporter: Ken McCracken
• Created: 07/Dec/11 20:16
• Updated: 28/Aug/22 13:03
• Resolved: 08/Dec/11 20:26

Description

FSDirectory.createOutput(..) uses a RandomAccessFile to do its work. On my system the default FSDirectory.open(..) creates an NIOFSDirectory. If createOutput is called on a segments_* file and a crash occurs between RandomAccessFile creation (file system shows a segments_* file exists but has zero bytes) but before any bytes are written to the file, subsequent IndexWriters cannot proceed. The difficulty is that it does not know how to clear the empty segments_* file. None of the file deletions will happen on such a segment file because the opening bytes cannot not be read to determine format and version.

An initial proposed patch file is attached below.