Hi there. Thanks for the input. I just pulled together a quick set of .NET console apps to test this out. I have an app that indexes and an app that holds an open searcher. Sure enough, after each incremental index/searcher refresh, I can't delete the old index files. I even tried doing a gc.collect(), with no luck.
I'm currently porting these two apps over to Java to see if I get different results; I'll post the code, and let you know what I find. Monsur > -----Original Message----- > From: Nestel, Frank IZ/HZA-IOL [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 28, 2005 7:31 PM > To: java-user@lucene.apache.org; lucene-user@jakarta.apache.org > Subject: RE: IndexSearcher hanging on to old index files in Windows > > Maybe it is .NET specific?! We use a very similar > Szenario with Java under Windows and the Server is > now running for 40 day since we launched it productively. > No problem at all! We have two index directories between > which we switch back and forth though? > > Frank > > >-----Original Message----- > >From: Monsur Hossain [mailto:[EMAIL PROTECTED] > >Sent: Friday, April 29, 2005 12:11 AM > >To: lucene-user@jakarta.apache.org > >Subject: IndexSearcher hanging on to old index files in Windows > > > > > > > >Hi all. I'm running Lucene.NET in a Windows/ASP.NET > >environment. We are searching a 300meg index in a web > >environment, where the IndexSearcher is cached. Every 10-30 > >minutes, a separate process updates the index. When ASP.NET's > >cache detects a changed index, it drops the current > >IndexSearcher (which the Garbage collector takes care of in > >the future [1]) and creates a new one. > > > >Now, while the index is being updated, the current > >IndexSearcher in cache holds a reference to the old index > >files. Therefore, the IndexWriter can't delete them, and they > >sit around in the folder, continuing to grow. Since the > >IndexSearcher is left to the GC, there's no guarantee of when > >the files will be released. > > > >I was considering such previously mentioned systems as > >reference counting [2] and swapping between two indexes [3]. > >But in both these cases, I don't think I'm ever guaranteed > >that an old IndexSearcher will have released its grasp on the > >old files in time to delete them. > > > >Anyway, I'd like to hear if others are dealing with this issue. > > > >Also, I'm curious, is this a Windows specific issue; I haven't > >seen any mention of this on UNIX? > > > >Thanks, > >Monsur > > > >[1] http://tinyurl.com/8qzo4 > >[2] http://tinyurl.com/8enzh > >[3] I can't find a link to it, but it was suggested by George > >Aroush in a previous thread of mine. > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
