failure is due to the IndexFileDeleter attempting to load
> > segments_93 to track referenced commit infos.
> >
> > Is this a state an IndexWriter could get the directory into, or does it
> > involve higher level interference (like copying files around)?
> >
&g
> segments_96 is referencing _8x ... _95
> >
> > The IndexWriter failure is due to the IndexFileDeleter attempting to load
> > segments_93 to track referenced commit infos.
> >
> > Is this a state an IndexWriter could get the directory into, or does it
> &g
volve higher level interference (like copying files around)?
>
> Tim
>
> On Thu, 14 Apr 2022 at 13:20, Baris Kazar wrote:
>
> > yes that is a great point to look at first and that would eliminate any
> > jdbc related issues that may lead to such problems.
> > Best r
a great point to look at first and that would eliminate any
> jdbc related issues that may lead to such problems.
> Best regards
>
> From: Tim Whittington
> Sent: Wednesday, April 13, 2022 9:17:44 PM
> To: java-user@lucene.apache.org
> Subje
yes that is a great point to look at first and that would eliminate any jdbc
related issues that may lead to such problems.
Best regards
From: Tim Whittington
Sent: Wednesday, April 13, 2022 9:17:44 PM
To: java-user@lucene.apache.org
Subject: Re: How to handle
That is a good practice and i pointed out that since i saw lucene 7.0 in the
stack trace.
Best regards
From: Tim Whittington
Sent: Wednesday, April 13, 2022 9:15 PM
To: java-user@lucene.apache.org
Subject: Re: How to handle corrupt Lucene index
To be clear
Thanks for this - I'll have a look at the database server code that is
managing the Lucene indexes and see if I can track it down.
Tim
On Thu, 14 Apr 2022 at 12:41, Robert Muir wrote:
> On Wed, Apr 13, 2022 at 8:24 PM Tim Whittington
> wrote:
> >
> > I'm working with/on a database system that
To be clear, these indexes are created and read with the same Lucene
version (7.3.0).
Tim
On Thu, 14 Apr 2022 at 12:45, Baris Kazar wrote:
> In my experience that if you built index at version x then use index also
> in version x.
> I never encountered any problems this way witj Lucene.
>
> Can
In my experience that if you built index at version x then use index also in
version x.
I never encountered any problems this way witj Lucene.
Can you maybe recreate lucene index on 7.3.0?
Also how do you use database in your scenario?
Are you using jdbc like operations like in Oracle database?
On Wed, Apr 13, 2022 at 8:24 PM Tim Whittington
wrote:
>
> I'm working with/on a database system that uses Lucene for full text
> indexes (currently using 7.3.0).
> We're encountering occasional problems that occur after unclean shutdowns
> of the database , resulting in
> "org.apache.lucene.index
10 matches
Mail list logo