[
https://issues.apache.org/jira/browse/LUCENENET-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shad Storhaug resolved LUCENENET-521.
-------------------------------------
Resolution: Fixed
Fix Version/s: Lucene.Net 4.8.0
A regression test
(https://github.com/apache/lucenenet/commit/39e63160efd6709c591862a7cf6c8e3a1e44b126)
was added to confirm the new MMapDirectory implementation doesn't have this
bug.
> Concurrency bug with MMapDirectory
> ----------------------------------
>
> Key: LUCENENET-521
> URL: https://issues.apache.org/jira/browse/LUCENENET-521
> Project: Lucene.Net
> Issue Type: Bug
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 3.0.3
> Environment: Visual Studio 2012, Lucene.Net 3.0.3 via Nudget, Windows
> 8 64bit, 4GB DDR3
> Reporter: Tamas Varga
> Fix For: Lucene.Net 4.8.0
>
> Attachments: _0.cfs, _0.cfx, segments_2, segments.gen
>
>
> It seems like mmapdirectory doesnt handle concurrency
> this works fine: http://pastebin.com/EQx0L23K
> This:http://pastebin.com/ay6B2Krp (note that the only diff is, that i changed
> the FsDirectory.Open(newDirInfo) to new MMapDirectory(newDirinfo) in line 12 )
> fails with exception:
> {System.ArgumentOutOfRangeException: Index was out of range. Must be
> non-2negative and less than the size of the collection.
> Full exception here: http://pastebin.com/erZTxH3d
> If in the second code example I set the concurrentTaskCount to 1, everything
> is just fine.
> Looks like a concurrency bug for me. Am I missing something?
> T
> Edit: I attached to content of the newMMap folder, after the index is created
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
