Simple question about concurrency

Hi, I'm still mostly a beginner, both with Java and Lucene, so I apologize if this may be dumb questions. Is making index-modifying operations safe as simple just doing the following? synchronized (writer) { while (IndexReader.isLocked(directory)) wait();

Concurrency in Lucene

Hi, I'm new in Lucene and I want to use in a website to manage some documentation: Bacally users can add or modify existing documents and users can search the documents. And I have some questions about concurrency, I have been reading the FAQ and searching the mailing list. But I still have some

RE: Concurrency

. in Windows, the file system name and file are managed as a single entity. Herb -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Saturday, February 28, 2004 1:22 PM To: Lucene Users List Subject: RE: Concurrency I'm not sure what happens on Windows, but this should

RE: Concurrency

that probably don't exist anymore? David Townsend -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: 20 February 2004 13:26 To: Lucene Users List Subject: Re: Concurrency Ive just got a couple of questions which i cant quite work out...wondered if someone

Concurrency

Hi Ive just got a couple of questions which i cant quite work out...wondered if someone could help me with them: 1. What happens if i make a backup (copy) of an index while documents are being added? Can it cause problems, and if so is there a way to safely do this? 2. When I create a new

Re: Concurrency

Ive just got a couple of questions which i cant quite work out...wondered if someone could help me with them: 1. What happens if i make a backup (copy) of an index while documents are being added? Can it cause problems, and if so is there a way to safely do this? You should be okay.

Re: Concurrency

Alan Smith wrote: 1. What happens if i make a backup (copy) of an index while documents are being added? Can it cause problems, and if so is there a way to safely do this? This is not in general safe. A copy may not be a usable index. The segments file points to the current set of files. An

Re: Concurrency

David Townsend wrote: Does this mean that if an IndexSearcher has hold of a segment file, then the index is optimised, any subsequent search will use a list of files that probably don't exist anymore? The IndexSearcher (through an IndexReader) has the files open, so it is still valid, and may be

Re: Concurrency

It would be great if we could come up with way to integrate the Lucene locking information with something more incremental like rsync. At Furl ( http://www.furl.net ) we have this problem in spades because we have thousands (and thousands) of indexes that need to be backed up. Currently, we

Concurrency

Thanks Doug and Otis. Thats very helpful. So if an IndexSearcher is open, new documents are just added to existing index files which remain under the same name yeah? And an IndexSearcher which continues to search these changed files will still return the same results (i.e. the modifications

Concurrency in Lucene.

I´m starting a new project using lucene where all forms filled by users are indexed and I ´m wondering about the possibility of concurrency problems... Have someone got concurrency problems using lucene? Any advice or experience's share will be inevaluable!! Regards, Flavio Regis de Arruda