Hi, My limited experience shows that reading/searching in a servlet at the "same" time as writing to the index from an application (e.g. by a scheduled script) works very well.
The only thing that has caused me problems is applications (e.g. cron started) writing to the index that "crash" while the write-lock is in effect. (The "crash" is in my case often cause by bad socket programming, and has nothing to do with Lucene.) The following scheduled applications will then, of cause, not be able to update the index. cheers Clas / frisim.com On Fri, 21 Jan 2005 09:57:22 -0500, Ashley Steigerwalt <[EMAIL PROTECTED]> wrote: > I am a little fuzzy on the thread-safeness of Lucene, or maybe just java. > From what I understand, and correct me if I'm wrong, Lucene takes care of > concurrency issues and it is ok to run a query while writing to an index. > > My question is, does this still hold true if the reader and writer are being > executed as separate programs? I have a cron job that will update the index > periodically. I also have a search application on a web form. Is this going > to cause trouble if someone runs a query while the indexer is updating? > > Ashley > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
