Hi Nick,
Have you managed to solve/recreate this issue?
There has been a recent progress on index corruption issues:
http://issues.apache.org/jira/browse/LUCENE-140
http://issues.apache.org/jira/browse/LUCENE-784
In those cases an application created FSDirectory with create=false
and created
Hi Doron,
sorry, forgot to include env... Here is env for test machine that create
the index:
- lucene 1.9.1
- ibm jdk 1.5 sr2
- RedHat enterprise linux release 4 (kernel 2.6.9-34ELsmp on x86_64)
- 8GB RAM
- 2 dual core xeon 3.4ghz.
- indexes on local disks, locks also on local (/tmp)
From the
I meant ~182K files ...
> Nick, could you provide additional info:
> (1) Env info - Lucene version, Java version, OS, JVM args (e.g. -XmNNN),
> etc...
> (2) is this reproducible? By the file sizes there seem to be ~182 indexed
> docs when the problem occur, so, if this is reproducible it would
hop
Nick, could you provide additional info:
(1) Env info - Lucene version, Java version, OS, JVM args (e.g. -XmNNN),
etc...
(2) is this reproducible? By the file sizes there seem to be ~182 indexed
docs when the problem occur, so, if this is reproducible it would hopefully
not take too long. If reprod
Hi, i sent this 30 min ago and it didn't seem to go through so i'm
trying again, i apologize if two copies finally arrive.
I am working on the development of a product that is using Lucene. A
corrupt index was reported by testers and it is in an odd state.
The indexes are built in batches (to mul
I am working on the development of a product that is using Lucene. A
corrupt index was reported by testers and it is in an odd state.
The indexes are built in batches (to multiple ram indexes in parallel)
and then eventually merged into a disk index with
IndexWriter.addIndexes(Directory[]).
Someho
