Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 42361 invoked from network); 8 Apr 2009 20:00:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Apr 2009 20:00:34 -0000 Received: (qmail 15892 invoked by uid 500); 8 Apr 2009 20:00:32 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 15809 invoked by uid 500); 8 Apr 2009 20:00:32 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 15799 invoked by uid 99); 8 Apr 2009 20:00:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Apr 2009 20:00:32 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.200.168] (HELO wf-out-1314.google.com) (209.85.200.168) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Apr 2009 20:00:23 +0000 Received: by wf-out-1314.google.com with SMTP id 29so300929wff.20 for ; Wed, 08 Apr 2009 12:59:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.89.13 with SMTP id m13mr571539wfb.50.1239220798149; Wed, 08 Apr 2009 12:59:58 -0700 (PDT) In-Reply-To: References: Date: Wed, 8 Apr 2009 15:59:58 -0400 Message-ID: <9ac0c6aa0904081259q2557fc00t62ed8443db6a5458@mail.gmail.com> Subject: Re: Lucene 1.4.3: Error when creating Searcher From: Michael McCandless To: java-user@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Likely your exception happened because a reader was trying to open just as a writer was committing, twice in a row. Do you commit (flush or close) frequently from your writer? As of 2.1, Lucene no longer uses a commit locks -- commits are now lockless, so you won't hit this on upgrading to 2.4. Mike On Wed, Apr 8, 2009 at 3:40 PM, Zhang, Lisheng wrote: > Hi, > > Sorry that my initial message is not clear, I read lucene source code (bo= th 1.4.3 > and 2.4.0), and understood more. > > The problem is that when using lucene 1.4.3 sometimes when searching, we = got > the error: > > Lock obtain timed out: Lock@/tmp/lucene-ba94511756a2670adeac03a50532c63c-= commit.lock > > It seems that in 2.4.0 we will never have this issue because this error c= an only > happen when concurrent writing. > > Is this true? > > Thanks very much for helps, Lisheng > > >> =A0-----Original Message----- >> From: =A0 =A0 =A0 =A0 Zhang, Lisheng >> Sent: Wednesday, April 08, 2009 9:08 AM >> To: =A0 'java-user@lucene.apache.org' >> Subject: =A0 =A0 =A0Lucene 1.4.3: Error when creating Searcher >> >> Hi, >> >> We are using lucene 1.4.3, sometimes when two threads try to search, >> one thread got error when creating MultiSearcher: >> >> Lock obtain timed out: Lock@/tmp/lucene-ba94511756a2670adeac03a50532c63c= -commit.lock >> >> I read lucene FAQ and searched previous discussions, it seems that this >> error should be related to indexing, but we are only creating Searcher? >> >> Thanks very much for helps, Lisheng >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org