lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Isakson" <>
Subject RE: Problem with long run IndexSearcher
Date Mon, 19 May 2003 14:18:39 GMT
bah, accidently sent that before I was finished typing...


which really should be added to the FAQ.

It just so happens that I spent a good deal of my weekend working on a class to solve this
problem. It hasn't been tested much and I'm new to writing apps that deal with threading issues
(so I don't know if I blundered anywhere). I'd love to see if it works and get feedback from
anyone that uses it.

See my message at:

If you have any feedback, pleass attach comments to the bug.


Eric D. Isakson        SAS Institute Inc.
Application Developer  SAS Campus Drive
XML Technologies       Cary, NC 27513
(919) 531-3639

-----Original Message-----
From: Eric Isakson [] 
Sent: Monday, May 19, 2003 10:05 AM
To: Lucene Developers List
Subject: RE: Problem with long run IndexSearcher


This problem stems from the fact that the IndexReader won't see your changed index.

See the faq entries:

-----Original Message-----
From: Giulio Cesare Solaroli [] 
Sent: Monday, May 19, 2003 9:38 AM
Subject: Problem with long run IndexSearcher

Hi all,

first let me express my compliments for Lucene.
I have been up for a full week-end to double check the results I was 
having because I couldn't belive what I saw; with a stupid application 
I could index DB data at a sustained rate of 50 documents per second.

Now we have more that 2 millions documents indexed and the performance 
are still excellent; our main bottle neck is still the DB.

Our situation:
- we are indexing new documents at a sustained rate (an average of 
40.000 new documents a day);
- we have written a small xmlRpc server in Java to search the index 
from other applications.

The xmlRpc server creates a single instance of IndexSearcher a reuse it 
for each query issued.
For each request, a new Query object is created and the documents found 
are returned to the client.

The problem we are seeing is that the documents indexed after the 
xmlRpc server is started will not be found until the server is 

Is this our foult, or the way IndexSearcher should work?

What is the best way to keep the IndexSearcher up to date with the 
updated index?

Thanks for your attention,

Giulio Cesare Solaroli

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message