someone explain why this is?
> Does Solr/Lucene cache the results of CheckIndex? Note that the
> attempt runs are on the same core with same segments.
This is indeed a Lucene question, but that doesn't mean it will get
ignored. If you want more detail than this, tr
run for the first
time, while subsequent runs are much much faster. Can someone explain why this
is? Does Solr/Lucene cache the results of CheckIndex? Note that the attempt
runs are on the same core with same segments.
Here are the results from attempt 1:
grep "check inte
f the Solr shards we are getting the error
> below.
> Both replicas of the shard had the same error.
> The shard index looked healthy:
> 1) It appeared active in the Solr admin page.
> 2) We could run searches against it.
> 3) No relevant errors where found in Solr logs.
> 4)
.
3) No relevant errors where found in Solr logs.
4) After we optimized the index in LUKE, CheckIndex did not report any
error.
My questions:
1) Is this is a real issue or a known bug in CheckIndex code that cause
false negative ?
2) Is there a known fix for this issue?
Here is the error we got
Hi -
with a corrupted core,
1. if I run CheckIndex with -fix, it will drop the hook to the corrupted
segment, but the segment files are still there, when we have a lot of
corrupted segments, we have to manually pick them out and remove them, is
there a way the tool can suffix them or prefix
Yeah that worked. Thanks!
-Original Message-
From: Ian Kallen [mailto:spidaman.l...@gmail.com]
Sent: Friday, January 08, 2010 5:32 PM
To: solr-user@lucene.apache.org
Subject: Re: checkindex
When I needed to use it, I couldn't find docs for it either but it's straight
forwa
When I needed to use it, I couldn't find docs for it either but it's straight
forward. Here's what I did:
un-jar the solr war file to find the lucene jar that solr was using and run
CheckIndex like this
java -cp lucene-core-2.9-dev.jar org.apache.lucene.index.CheckIndex
/pa
I've seen many mentions of the Lucene CheckIndex tool, but where can I find it?
Is there any documentation on how to use it?
I noticed Luke has it built-in, but I can't get Luke to open my index with the
"Don't open IndexReader(when opening corrupted index)" option chec
