Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 4809 invoked from network); 16 Oct 2003 20:08:47 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Oct 2003 20:08:47 -0000 Received: (qmail 59611 invoked by uid 500); 16 Oct 2003 20:08:33 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 59585 invoked by uid 500); 16 Oct 2003 20:08:33 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 59572 invoked from network); 16 Oct 2003 20:08:33 -0000 Received: from unknown (HELO mailshell.com) (209.157.66.245) by daedalus.apache.org with SMTP; 16 Oct 2003 20:08:33 -0000 Received: (qmail 20350 invoked from network); 16 Oct 2003 20:08:38 -0000 Received: from unknown (HELO lucene.com) (dcutting@grandcentral.com@12.210.200.74) by mail.mailshell.com with SMTP; 16 Oct 2003 20:08:38 -0000 Message-ID: <3F8EFAC5.5000806@lucene.com> Date: Thu, 16 Oct 2003 13:08:37 -0700 From: Doug Cutting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lucene Developers List Subject: Re: Index locked for write References: <2874E346-F69B-11D7-9BDA-000393760B7E@mac.com> In-Reply-To: <2874E346-F69B-11D7-9BDA-000393760B7E@mac.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N petite_abeille wrote: > I have been using 1.3 RC1 without any problem. But... since updating to > the cvs version, I'm getting a lot of apparently random IOException > related to locking: > > java.io.IOException: Index locked for write: > Lock@/tmp/lucene-5b228139f8fe55f7c74441a7d59f8f89-write.lock > at org.apache.lucene.index.IndexWriter.(IndexWriter.java:173) > at org.apache.lucene.index.IndexWriter.(IndexWriter.java:150) I don't know if you've already resolved this problem, but if you haven't, it may be related to the change in lock file implementations. Since the lock file is now stored in a different place than the index, it might be possible to remove an index directory, yet still have a lock file for it. Could that be what's happening here? Also, you asked if it was possible to disable locking, and the answer is yes. Check out FSDirectory.java for details. Doug --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org