ot be a problem as an IndexReader will be opened, not a
second IndexWriter.
Ross
-Original Message-
From: Dan Armbrust [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 02, 2005 3:10 PM
To: java-user@lucene.apache.org
Subject: Re: how long should optimizing take
You should be careful, ho
You should be careful, however, not to end up with two VM instances each
trying to open an index writer at the same time - one of them is going
to fail.
Aka, if someone using your web interface tries to add a new document to
the index while you have the optimizer running standalone, the web
i
n a weekly bases.
Ross
-Original Message-
From: Dan Armbrust [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 02, 2005 11:10 AM
To: java-user@lucene.apache.org
Subject: Re: how long should optimizing take
I would run your optimize process in a separate thread, so that your web
client doesn
10:42 AM
> To: 'java-user@lucene.apache.org'
> Subject: how long should optimizing take
>
>
> Hi,
>
> I'm having problems with the Lucene optimization. Two of the indexes are
> about 2BG big and every day about 30 documents are added to each of these
> inde
e up again as I haven't resolved it yet and
haven't found what's causing it.
Any help, ideas or sharing experience are welcome!
Thanks,
Ross
-Original Message-
From: Angelov, Rossen
Sent: Friday, May 27, 2005 10:42 AM
To: 'java-user@lucene.apache.org'
Subject: ho
er@lucene.apache.org'
Subject: how long should optimizing take
Hi,
I'm having problems with the Lucene optimization. Two of the indexes are
about 2BG big and every day about 30 documents are added to each of these
indexes. At the end of the indexing the IndexWriter optimize() method is
Hi,
I'm having problems with the Lucene optimization. Two of the indexes are
about 2BG big and every day about 30 documents are added to each of these
indexes. At the end of the indexing the IndexWriter optimize() method is
executed and it takes about 30 minutes to finish the optimization for each
