One more question: when you run CheckIndex, are you enabling asserts?
(java -ea:org.apache.lucene)?
Mike
James Brady wrote:
Thanks for your answers Michael! I was using a pre-1.3 Solr build,
but I've
now upgraded to the 1.3 release, run the new CheckIndex shipped as
part of
the Lucene
James Brady wrote:
Thanks for your answers Michael! I was using a pre-1.3 Solr build,
but I've
now upgraded to the 1.3 release, run the new CheckIndex shipped as
part of
the Lucene 2.4 dev build and I'm still getting the
CorruptIndexException:
docs out of order exceptions I'm afraid.
Di
Thanks for your answers Michael! I was using a pre-1.3 Solr build, but I've
now upgraded to the 1.3 release, run the new CheckIndex shipped as part of
the Lucene 2.4 dev build and I'm still getting the CorruptIndexException:
docs out of order exceptions I'm afraid.
Upon a fresh start, on newly Che
Actually, even in 2.3.1, CheckIndex checks for docs-out-of-order both
within and across segments, so now I'm at a loss as to why it's not
catching your case. Any of these indexes small enough to post
somewhere i could access?
Mike
James Brady wrote:
Hi,My indices sometime become corr
This is spooky!
First off, why are you hitting so much index corruption? Many classes
of failure (unhandled exception exits JVM, JVM killed or SEGVs, OS
crashes, power cord is pulled, etc.) should never result in index
corruption. Other failures (bad RAM, bad hard drives) can easily
ca
Hi,My indices sometime become corrupted - normally when Solr has to be
KILLed - these are not normally too much of a problem, as
Lucene's CheckIndex tool can normally detect missing / broken segments and
fix them.
However, I now have a few indices throwing errors like this:
INFO: [core4] webapp=/
