lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (JIRA)" <>
Subject [jira] [Commented] (LUCENENET-521) Concurrency bug with MMapDirectory
Date Sat, 04 May 2013 19:08:16 GMT


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. [].

The next version of Lucene.Net will have a properly implemented MemoryMappedDirectory.
> Concurrency bug with MMapDirectory
> ----------------------------------
>                 Key: LUCENENET-521
>                 URL:
>             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,
>            Reporter: Tamas Varga
>            Priority: Blocker
>         Attachments: _0.cfs, _0.cfx, segments_2, segments.gen
> It seems like mmapdirectory doesnt handle concurrency
> this works fine:
> This: (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:
> If in the second code example I set the concurrentTaskCount to 1, everything is just
> 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:

View raw message