lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Engels" <reng...@ix.netcom.com>
Subject RE: Nio File Caching & Performance Test
Date Mon, 05 Jun 2006 23:50:00 GMT
Not that I know how. I think you are at the mercy of the GC. The files will
get deleted on the next merge though (most likely). 

-----Original Message-----
From: Peter Keegan [mailto:peterlkeegan@gmail.com] 
Sent: Thursday, June 01, 2006 6:23 PM
To: java-dev@lucene.apache.org; rengels@ix.netcom.com
Subject: Re: Nio File Caching & Performance Test

My search process is using MMapDirectory on a read-only index via:

-Dorg.apache.lucene.FSDirectory.class=org.apache.lucene.store.MMapDirectory

Another indexing process is building the next version of the index in a
different directory. When it's time to switch to the new index, the search
process closes the old IndexSearcher, MultiReader (2) and FSDirectories (2)
and opens the new index. Subsequently, attempts to delete the old index
files fail because there are apparently still references to them from the
old MMapDirectory (the deletes succeed when using FSDirectory).

My understanding is that the file mapping is valid until the underlying
buffer is garbage-collected. Is there a deterministic way of releasing the
old memory mapped files so that they can be deleted sucessfully?

Thanks,
Peter


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message