Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Thu, 16 Mar 2006 19:12:12 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-user@lucene.apache.org
Subject: Re: restart interrupted index
In-Reply-To: <6026e8b0603161904u3da97afcj479076f738b08510@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0603161910150.23727@hal.rescomp.berkeley.edu>
References: <BE07D857-20DA-44E4-AF91-1DF7BC4BEBA3@mac.com>
 <Pine.LNX.4.58.0603161856140.23126@hal.rescomp.berkeley.edu>
 <6026e8b0603161904u3da97afcj479076f738b08510@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: If I interrupt my IndexWriter with a kill signal, must of the time I
: will be left with a lock file AND corrupted index files (the searcher
: will throw some IllegalStateExceptions after the lock file is
: deleted).

if you are trying to deal with teh possibility that your indexing process
might crash hard, then there's not much you can do about the possibiity of
your index getting corrupted ... that's where backups are useful.

if you are trying to have a way to "cancel" your indexing process and then
start again later that's not really an issue with lucene -- you just need
a cleaner way to notify your application that you want it to stop, close
whatever IndexWriter/IndexReader you may be useing and shutdown cleanly.


-Hoss


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