Investigate Failing Test: Lucene.Net.Index.TestIndexWriterOnJRECrash::TestNRTThreads_Mem() #894
Labels
is:bug
is:task
A chore to be done
pri:normal
test-failure
up-for-grabs
This issue is open to be worked on by anyone
Comments
NightOwl888
added
up-for-grabs
NightOwl888
added a commit
to NightOwl888/lucenenet
that referenced
this issue
Jan 14, 2024
…ed [AwaitsFix] attribute because this test fails intermittently (see apache#894).
NightOwl888
added a commit
that referenced
this issue
Jan 14, 2024
…ed [AwaitsFix] attribute because this test fails intermittently (see #894).
1 task
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
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) 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
UninterrruptableMonitorinstead oflockstatements, but since a lock may be taken in any library we depend on that may throwThreadInterruptedExceptionfrom 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.The text was updated successfully, but these errors were encountered: