You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by lu...@jakarta.apache.org on 2004/06/05 16:32:28 UTC

[Jakarta Lucene Wiki] Updated: ConcurrentAccessToIndex

   Date: 2004-06-05T07:32:28
   Editor: 195.29.135.159 <>
   Wiki: Jakarta Lucene Wiki
   Page: ConcurrentAccessToIndex
   URL: http://wiki.apache.org/jakarta-lucene/ConcurrentAccessToIndex

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -4,10 +4,6 @@
 
 Things of course were slower but not by much.
 
-The trick is not to create another IndexSearcher while the other process is writing to the index.
-
-(OG: who wrote this?  I don't think this is 100% correct.  You should be able to create any number of IndexSearchers while an index is being merged or modified in any other way.  It's not always a good thing to do that, but as far as I know, it can be done without breaking anything.)
-
-I think he may have meant "IndexWriter" instead of "IndexSearcher" in the last sentence.
+The trick is not to create another IndexWriter while the other process is writing to the index.
 
 Also see LockObtainTimedOut for more info on how to debug the inability to obtain a lock for an index.

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