Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of ian.lea@gmail.com designates
 209.85.220.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=elMT3KIe4c5cdbdRiju8TgmpjGU6FbVoZnI3L3hR1gH2W0slLhA9HWc0T097KshOLW
         iTpzwfO8iy7996AKenQKIJRD6x+d5LDLbs4JtNI2/0QDslstHC0wXt6sICDOOSe739n7
         eW2vW+6o+5JfMh8OzRVLuQk0BAodvdI/Ti+sM=
MIME-Version: 1.0
In-Reply-To: <3836ec640911250737p8128f37nb7e92b408ef46cc2@mail.gmail.com>
References: <7ac523660911250713r6c6942f0vc1d044a4a503140a@mail.gmail.com>
	<8c4e68610911250731v1a62f3d8s6d22e311310a8a43@mail.gmail.com>
	<3836ec640911250737p8128f37nb7e92b408ef46cc2@mail.gmail.com>
From: Ian Lea <ian.lea@gmail.com>
Date: Wed, 25 Nov 2009 15:44:10 +0000
Message-ID: <8c4e68610911250744l15173a9al5d7f0680b62e481a@mail.gmail.com>
Subject: Re: best way to ensure IndexWriter won't corrupt the index?
To: java-user@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yes, good point. Messing around with lucene locking may well be a  way
to get corrupt indexes.  Any others?


--
Ian.


On Wed, Nov 25, 2009 at 3:37 PM, Max Lynch <ihasmax@gmail.com> wrote:
> On Wed, Nov 25, 2009 at 9:31 AM, Ian Lea <ian.lea@gmail.com> wrote:
>
>> > What are the typical scenarios when the index will go corrupt?
>>
>> Dodgy disks.
>>
>
> I also have had index corruption on two occasions. =A0It is not a big dea=
l for
> me since my data is fairly real time so the old documents aren't as
> important.
>
> However, I'm running this on a VPS with slicehost, so whether or not they
> use dodgy disks is not something I can confirm or even deal with.
>
> I do need to upgrade to 2.9 from 2.4, but I think one of the reasons for =
my
> index corruption is deleting the index.write file rather than removing th=
e
> lock through the Lucene APIs. =A0This seems like it could be a cause of
> corruption, correct?

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