[
https://issues.apache.org/jira/browse/LUCENENET-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647583#action_12647583
]
Grimace of Despair commented on LUCENENET-112:
----------------------------------------------
I'm really ignorant when it comes to Lucene source code, but I saw the release
notes of Lucene 2.4.0 containing something very important to me:
"A machine or OS crash, or power loss, while IndexWriter is writing to an index
will no longer corrupt the index."
Then I dug into jira and found this one and thought they might relate. I mean:
maybe those changes will invalidate this issue?
> orphan IndexWriter locks
> ------------------------
>
> Key: LUCENENET-112
> URL: https://issues.apache.org/jira/browse/LUCENENET-112
> Project: Lucene.Net
> Issue Type: Bug
> Reporter: Digy
> Attachments: SimpleFSLockFactory.patch, TestLockFactory.patch
>
>
> If an application crashes while an IndexWriter is open, it leaves the lock
> file(writer.lock) behind. Re-running the application results in an "Lock
> obtain timeout" exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
