[LUCENE-3028] IW.getReader() returns inconsistent reader on RT Branch

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Realtime Branch
• Fix Version/s: Realtime Branch
• Component/s: core/index
• Lucene Fields: New, Patch Available
• Assignee: Simon Willnauer
• Reporter: Simon Willnauer
• Created: 14/Apr/11 10:30
• Updated: 28/Aug/22 12:44
• Resolved: 03/May/11 15:47

Description

I extended the testcase TestRollingUpdates#testUpdateSameDoc to pull a NRT reader after each update and asserted that is always sees only one document. Yet, this fails with current branch since there is a problem in how we flush in the getReader() case. What happens here is that we flush all threads and then release the lock (letting other flushes which came in after we entered the flushAllThread context, continue) so that we could concurrently get a new segment that transports global deletes without the corresponding add. They sneak in while we continue to open the NRT reader which in turn sees inconsistent results.

I will upload a patch soon

Issue Links

• blocks: LUCENE-2324 Per thread DocumentsWriters that write their own private segments