ubject: Re: Index files not deleted after optimization
> On Tue, Nov 3, 2009 at 9:45 AM, Ganesh wrote:
>> My IndexReader and Searcher is open all the time. I am reopening it at
>> constant interval.
>>
>> Below are the code sequence.
>>
>> 1. DB optimize
>
On Tue, Nov 3, 2009 at 9:45 AM, Ganesh wrote:
> My IndexReader and Searcher is open all the time. I am reopening it at
> constant interval.
>
> Below are the code sequence.
>
> 1. DB optimize
> 2. Close writer
> 3. Open writer
> 4. Reopen new reader
> 5. Close old reader
> 6. Close old searcher.
c/pid/fd/.
>
> searcher.getIndexReader().close();
> searcher.close();
>
> Regards
> Ganesh
>
> - Original Message -
> From: "Michael McCandless"
> To:
> Sent: Monday, November 02, 2009 6:03 PM
> Subject: Re: Index files not deleted after
se();
> searcher.close();
>
> Regards
> Ganesh
>
> - Original Message -
> From: "Michael McCandless"
> To:
> Sent: Monday, November 02, 2009 6:03 PM
> Subject: Re: Index files not deleted after optimization
>
>
> Something must still have these file ha
nt: Monday, November 02, 2009 6:03 PM
Subject: Re: Index files not deleted after optimization
Something must still have these file handles open at the time the
optimization completed.
EG do you have a reader open on this index?
Mike
On Mon, Nov 2, 2009 at 6:54 AM, Ganesh wrote:
> Hello all,
&
Something must still have these file handles open at the time the
optimization completed.
EG do you have a reader open on this index?
Mike
On Mon, Nov 2, 2009 at 6:54 AM, Ganesh wrote:
> Hello all,
>
> I am using Lucene 2.4.1 and My app is running inside Tomcat.
>
> In Windows, after database o
