lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7582) NIOFSDirectory sometime doesn't work on windows
Date Tue, 06 Dec 2016 11:11:29 GMT


Uwe Schindler commented on LUCENE-7582:

use static factory. It will choose the best implementation automatically
depending on Operating System. On Windows this will choose MMapDircetory for 64 bit platforms
and SimpleFSDirectory on 32 bit platforms. This is perfectly fine. Keep in min that SImpleFSDirectory
is not "slow" , it just does not perform well in multithreaded environments (many parallel
searches). But on 32 bit platforms it is unlikely that you have many parallel searches! 32
bit VMs are mostly used for stuff like local mail search engines or other pure client/GUI

Async FileChannel does not work and slows down immense for synchronous IO like Lucene does,
because you need additional client code synchronization. It gets like 2 times slower than

> NIOFSDirectory sometime doesn't work on windows
> -----------------------------------------------
>                 Key: LUCENE-7582
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/store
>    Affects Versions: 5.3.1
>         Environment: Windows 10, 32 bits JVM
>            Reporter: Kevin Senechal
> Hi!
> I've an error using lucene on windows. I already post a question on modeshape forum (
and it looks that NIOFSDirectory is not working well on windows as described in the java documentation
of this class.
> {quote}NOTE: NIOFSDirectory is not recommended on Windows because of a bug in how
is implemented in Sun's JRE. Inside of the implementation the position is apparently synchronized.
See here for details.{quote}
> After reading the linked java issue (,
it seems that there is a workaround to solve it, use an AsynchronousFileChannel.
> Is it a choice that has been made to not use AsynchronousFileChannel or will it be a
good fix?
> You'll find the complete stacktrace below:
> {code:java}
> Caused by: org.modeshape.jcr.index.lucene.LuceneIndexException: Cannot commit index writer
>   at org.modeshape.jcr.index.lucene.LuceneIndex.commit( ~[dsdk-launcher.jar:na]
>   at org.modeshape.jcr.spi.index.provider.IndexChangeAdapter.completeWorkspaceChanges(
>   at org.modeshape.jcr.cache.change.ChangeSetAdapter.notify(
>   at org.modeshape.jcr.spi.index.provider.IndexProvider$AtomicIndex.notify(
>   at org.modeshape.jcr.bus.RepositoryChangeBus.notify( ~[dsdk-launcher.jar:na]
>   at org.modeshape.jcr.cache.document.WorkspaceCache.changed(
>   at org.modeshape.jcr.txn.SynchronizedTransactions.updateCache(
>   at
>   at ~[dsdk-launcher.jar:na]
>   ... 19 common frames omitted  
> Caused by: java.nio.file.FileSystemException: C:\Users\Christopher\Infiltrea3CLOUDTEST8\\indexes\default\nodesByPath\_dc_Lucene50_0.doc:
The process cannot access the file because it is being used by another process.  
>   at sun.nio.fs.WindowsException.translateToIOException( ~[na:1.8.0_92]
>   at sun.nio.fs.WindowsException.rethrowAsIOException( ~[na:1.8.0_92]
>   at sun.nio.fs.WindowsException.rethrowAsIOException( ~[na:1.8.0_92]
>   at sun.nio.fs.WindowsFileSystemProvider.newFileChannel(
>   at ~[na:1.8.0_92]  
>   at ~[na:1.8.0_92]  
>   at org.apache.lucene.util.IOUtils.fsync( ~[dsdk-launcher.jar:na] 

>   at ~[dsdk-launcher.jar:na]
>   at ~[dsdk-launcher.jar:na]
>   at
>   at org.apache.lucene.index.IndexWriter.startCommit( ~[dsdk-launcher.jar:na]
>   at org.apache.lucene.index.IndexWriter.prepareCommitInternal(
>   at org.apache.lucene.index.IndexWriter.commitInternal( ~[dsdk-launcher.jar:na]
>   at org.apache.lucene.index.IndexWriter.commit( ~[dsdk-launcher.jar:na]
>   at org.modeshape.jcr.index.lucene.LuceneIndex.commit( ~[dsdk-launcher.jar:na]

> {code}
> Thank you in advance for your help

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message