[ https://issues.apache.org/jira/browse/LUCENE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero updated LUCENE-2095: ------------------------------------ Attachment: lucene-stresstest.patch attaching the testcase, apply to version 2.9.1. It's slow, please be patient. > Document not guaranteed to be found after write and commit > ---------------------------------------------------------- > > Key: LUCENE-2095 > URL: https://issues.apache.org/jira/browse/LUCENE-2095 > Project: Lucene - Java > Issue Type: Bug > Components: Index > Affects Versions: 2.4.1, 2.9.1 > Environment: Linux 64bit > Reporter: Sanne Grinovero > Attachments: lucene-stresstest.patch > > > after same email on developer list: > "I developed a stress test to assert that a new document containing a > specific term "X" is always found after a commit on the IndexWriter. > This works most of the time, but it fails under load in rare occasions. > I'm testing with 40 Threads, both with a SerialMergeScheduler and a > ConcurrentMergeScheduler, all sharing a common IndexWriter. > Attached testcase is using a RAMDirectory only, but I verified a > FSDirectory behaves in the same way so I don't believe it's the > Directory implementation or the MergeScheduler. > This test is slow, so I don't consider it a functional or unit test. > It might give false positives: it doesn't always fail, sorry I > couldn't find out how to make it more likely to happen, besides > scheduling it to run for a longer time." > I tested this to affect versions 2.4.1 and 2.9.1; -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org