[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    Re: potential synchronization problem
From:       Leos Literak <literakl () centrum ! cz>
Date:       2004-04-30 12:10:04
Message-ID: c6tflg$rn5$1 () sea ! gmane ! org
[Download RAW message or body]

Otis Gospodnetic wrote:
> Yes.
> I suggest you devise a 'index request queue' mechanism to handle
> situations like this.  This can probably be made quite generic (i.e.
> not Lucene and not indexing specific).  How you go about implementing
> this is up to.

I handle this with script, which
1\ generates new index to temporary directory
2\ removes directory with old index
3\ renames temporary directory to standard location

unfortunatelly this doesn't garantee atomicity, so
I can find in logs exceptions, when user performed
search in 2\ or 3\ steps. Because step 1\ takes
ten minutes, while 2\ and 3\ several seconds at most,
I am happy with this solution.

Leos


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]