Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of
 mailing.patrick.kimber@gmail.com designates 64.233.162.237 as permitted
 sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=BfkzlAfNnW9I4hKptXELcRAOBbmrdkhwUbHzMsGioVDgFf8/ZUWi5EWZSHXSbTg9qxlUKJmLhu8pnVBw3/5rVtg8sKHjcn8HWzLzxLyuu71Efc5ufJsRpyekq+5sufeJ42mvUAQU3F/HaCnj7X+Bk+jNmkuJCpDZ3arC/SyfEL4=
Message-ID: <4f9b23800707050720o1661900fle3ac06cfae6e28ad@mail.gmail.com>
Date: Thu, 5 Jul 2007 15:20:25 +0100
From: "Patrick Kimber" <mailing.patrick.kimber@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: Lucene 2.2, NFS, Lock obtain timed out
In-Reply-To: <1183544020.31233.1198452157@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <OF19D3F11C.A08B201A-ON6525730D.003B9E55-6525730D.003DD835@hewitt.com>
	 <1183461674.2220.1198268681@webmail.messagingengine.com>
	 <4f9b23800707030432i1067a67auc8fc0f83abeeea0@mail.gmail.com>
	 <1183465207.11743.1198277029@webmail.messagingengine.com>
	 <4f9b23800707030650y6139a19fn2870bef783636f46@mail.gmail.com>
	 <4f9b23800707030813m998f3e5u1984d913f51d13b6@mail.gmail.com>
	 <1183476448.14138.1198311153@webmail.messagingengine.com>
	 <4f9b23800707040028g209341f8l24ce8363723d9729@mail.gmail.com>
	 <1183544020.31233.1198452157@webmail.messagingengine.com>

Hi Michael

Just to let you know, I am on holiday for one week so will not be able
to send a progress report until I return.

I have deployed the new code to a test site so I will be informed if
the users notice any issues.

Thanks for your help

Patrick


On 04/07/07, Michael McCandless <lucene@mikemccandless.com> wrote:
>
> "Patrick Kimber" <mailing.patrick.kimber@gmail.com> wrote:
>
> > Yes, there are many lines in the logs saying:
> > hit FileNotFoundException when loading commit "segment_X"; skipping
> > this commit point
> > ...so it looks like the new code is working perfectly.
>
> Super!
>
> > I am sorry to be vague... but how do I check which segments file is
> > opened when a new writer is created?
>
> Oh, sorry, it's not exactly obvious.  Here's what to look for:
>
> On machine #1 (the machine that added docs & then closed its writer)
> you should see lines like this, which are printed every time the
> writer flushes its docs:
>
>     checkpoint: wrote segments file "segments_X"
>
> Find the last such line on machine #1 before it closes the writer, and
> that's the "current" segments_X in the index.
>
> Then on machine #2 (the machine that immediately opens a new writer
> after machine #1 closed its writer) you should see a line like this:
>
>     org.apache.lucene.index.IndexFileDeleter@XXXXXXX main: init: current segments file is "segments_Y"
>
> which indicates which segments file was loaded by this writer.  The
> thing to verify is that X is always equal to Y whenever a writer
> quickly moves from machine #1 to machine #2.
>
> > I will add a check to my test to see if all documents are added.  This
> > should tell us if any documents are being silently lost.
>
> Very good!  Keep us posted, and good luck,
>
> Mike
>
> ---------------------------------------------------------------------
> 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