NightOwl888 opened a new issue, #894: URL: https://github.com/apache/lucenenet/issues/894
### Is there an existing issue for this? - [X] I have searched the existing issues ### Task description This test was ported and added in #786 (to close #768). Unfortunately, it fails intermittently. A user shared in [Lucene.net corrupted index (segments.gen)](https://stackoverflow.com/questions/77525791/lucene-net-corrupted-index-segments-gen) on StackOverflow that this appears to be due to a real problem that happens in production. The failure may or may not be related to the deprecation of thread interrupts (#555) in Lucene.NET which were supported in the Java version. We make a best effort to support them using `UninterrruptableMonitor` instead of `lock` statements, but since a lock may be taken in any library we depend on that may throw `ThreadInterruptedException` from the action of taking a lock, we cannot 100% guarantee that we can catch every one of these exceptions in order to rollback an in-process commit. In Java, taking a lock does not throw an exception in any case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@lucenenet.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
