lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson" <erickerick...@gmail.com>
Subject Re: Index issue with unexpected termination of program without optimizing the index.
Date Mon, 25 Jun 2007 13:13:34 GMT
In this case, it seems that everything is under your control and you
can gracefully close the Lucene index down when this occurs. Which
I would recommend under any circumstances so as to insure that you
know the state of your index.

At issue here is whether the last N documents that you've indexed
are actually written to disk when the program terminates if it terminates
ungracefully. The only way you can answer this for certain is if you close
the index explicitly, which will flush all pending documents to disk...

Best
Erick

On 6/25/07, Sonu SR <sonusr@gmail.com> wrote:
>
> Hi,
> Thanks for the response. The error is probably related with mysql. My
> appliation using mysql for keeping the status of indexed documents. So
> that
> duplication can be avoided.  Some times the mysql connection has been
> lost,
> and the program terminated.
>
> Sonu
>
>
> On 6/25/07, Otis Gospodnetic <otis_gospodnetic@yahoo.com> wrote:
> >
> > Hi,
> > How exactly is your application terminating?  Is there an error?  An
> > exception?  If so, please provide the stack trace to get a better/right
> > answer.
> >
> > No, the index is not automatically optimized at the beginning of
> indexing.
> > There are likely no issues with documents that were already indexed and
> > were written to disk before your application terminated.
> > There are no explicit transactions in Lucene, but in nearly 8 years of
> > using Lucene I've never personally experienced Lucene index corruption.
> >
> > Otis
> > --
> > Lucene Consulting -- http://lucene-consulting.com/
> >
> >
> >
> > ----- Original Message ----
> > From: Sonu SR <sonusr@gmail.com>
> > To: java-user@lucene.apache.org
> > Sent: Monday, June 25, 2007 1:16:46 PM
> > Subject: Index issue with unexpected termination of program without
> > optimizing the index.
> >
> > Hi,
> >
> > I am using lucene in our site for index and search. We are creating the
> > index with large collection of documents (XML). The program some times
> > terminating without completing the index process. So the index
> > optimization
> > and closing is not properly done. Is it to be optimized on the next
> index
> > time? Is there any issue with the existing indexed documents? Is there
> any
> > transaction management in lucene?
> >
> > Thanks,
> > Sonu
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-user-help@lucene.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message