Return-Path: Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 23692 invoked from network); 27 Sep 2001 18:03:12 -0000 Received: from unknown (HELO mta.12.com) (65.198.8.41) by daedalus.apache.org with SMTP; 27 Sep 2001 18:03:12 -0000 Received: (qmail 23886 invoked from network); 27 Sep 2001 18:00:39 -0000 Received: from unknown (HELO riker.grandcentral.com) (10.102.15.55) by mta.12.com with SMTP; 27 Sep 2001 18:00:39 -0000 Received: by mail.grandcentral.com with Internet Mail Service (5.5.2653.19) id ; Thu, 27 Sep 2001 10:53:22 -0700 Message-ID: <4BC270C6AB8AD411AD0B00B0D0493DF0EE7BE2@mail.grandcentral.com> From: Doug Cutting To: 'Scott Ganyo' , "'lucene-dev@lists.sourceforge.net'" Cc: "'lucene-dev@jakarta.apache.org'" Subject: RE: [Lucene-dev] Index integrity check and fix? Date: Thu, 27 Sep 2001 10:53:20 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: Scott Ganyo [mailto:scott.ganyo@eTapestry.com] > > We're still having occasional problems with indexes getting the > error (in Lucene 1.1 release): > java.io.IOException: /index/_1x7f.fnm already exists > when updating records. I'm not positive where this is coming from, > but I'm guessing that it is from when we have to forcefully stop the > service since all access to the index is synchronized. With the file locking code that I just checked in (to Jakarta, not Sourceforge) you should not have this problem anymore. Instead, if Java exits unexpectedly, you might now find a .lock file left in the index that will prevent restart. In this case, I recommend removing all .lock files before restarting your application, when you are certain that no applications are currently accessing the index. Is that acceptable? BTW, this is the last message I will send to lucene-dev@lists.sourceforge.net. Henceforth I will use lucene-dev@jakarta.apache.org. Please subscribe to that list if you would like to stay involved with Lucene development. The Jakarta lucene-user list and Lucene website are still under construction, but Lucene development has moved to Jakarta. Doug