[ 
https://issues.apache.org/jira/browse/LUCENENET-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649141#comment-13649141
 ] 

Christopher Currens commented on LUCENENET-521:
-----------------------------------------------

[~sisve] - That's right, but to be clear, 2.9.4g uses memory-mapped files, the 
clean 2.9.4 release, which is what 3.0.3 was based on, uses the same 
MemoryStream objects that were originally ported in an earlier version. 
[https://svn.apache.org/repos/asf/lucene.net/tags/Lucene.Net_2_9_4_RC3/src/core/Store/MMapDirectory.cs].

The next version of Lucene.Net will have a properly implemented 
MemoryMappedDirectory.
                
> 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
>            Priority: Blocker
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to