"Martin Kobele" <[EMAIL PROTECTED]> wrote: > I was trying to find an answer to this. > I call IndexReader.deleteDocument() for the _first_ time. > If my index has several segments, my IndexReader is actually a MultiReader. > Therefore the variable directoryOwner is set to true and as the first step, a > lock file is created. After that, the document is marked as deleted. > > If I call deleteDocument again, it may or may not work. > Now by just reading the code, and I am sure I am missing some details, I am > wondering, how can I successfully call deleteDocument again? The code will > try to obtain the lockfile again, but since it is already there, it will time > out. That is the point where I am confused. After I deleted a document, the > write.lock file is still there, and directoryOwner is still true.
The lock should be acquired only on the first call to deleteDocument. That method calls acquireWriteLock which only acquires the write lock if it hasn't already (ie, writeLock == null). So the 2nd call to deleteDocument would see that the lock was already held and should not then try to acquire it again. You are only using a single instance of IndexReader, right? If for example you try to make a new instance of IndexReader and then call deleteDocument on that new one, then you would hit the exception unless you had closed the first one. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
