[ https://issues.apache.org/jira/browse/LUCENE-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless updated LUCENE-1130: --------------------------------------- Attachment: LUCENE-1130.take2.patch Attached take2 patch. I created a few more disk full threaded stress tests, whereby multiple threads are indexing, at some point start hitting disk full, but keep on trying to add docs for a while after that disk full. This uncovered a number of sneaky thread safety issues with how DocumentsWriter was handling exceptions, aborting, etc.. I've fixed them, and all tests pass. I'll wait another day before committing. > Hitting disk full during DocumentWriter.ThreadState.init(...) can cause hang > ---------------------------------------------------------------------------- > > Key: LUCENE-1130 > URL: https://issues.apache.org/jira/browse/LUCENE-1130 > Project: Lucene - Java > Issue Type: Bug > Components: Index > Affects Versions: 2.3 > Reporter: Michael McCandless > Assignee: Michael McCandless > Fix For: 2.3 > > Attachments: LUCENE-1130.patch, LUCENE-1130.take2.patch > > > More testing of RC2 ... > I found one case, if you hit disk full during init() in > DocumentsWriter.ThreadState, when we first create the term vectors & > fields writer, such that subsequent calls to > IndexWriter.add/updateDocument will then hang forever. > What's happening in this case is we are incrementing nextDocID even > though we never call finishDocument (because we "thought" init did not > succeed). Then, when we finish the next document, it will never > actually write because missing finishDocument call never happens. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]