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.
Did you create a new index after upgrading? Or are you saying that
the CheckIndex in Lucene 2.4 is also failing to catch the "docs out of
order" corruption in your original index?
Upon a fresh start, on newly Checked indices, I actually get a lot of
Exceptions like:
But when you ran CheckIndex it made no fixes to the index? (you said
"newly Checked").
SEVERE: java.lang.RuntimeException: [was class
org.mortbay.jetty.EofException] null
at
com
.ctc
.wstx.util.ExceptionUtil.throwRuntimeException(ExceptionUtil.java:18)
at
com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:731)
at
com
.ctc
.wstx.sr.BasicStreamReader.safeFinishToken(BasicStreamReader.java:
3657)
at
com.ctc.wstx.sr.BasicStreamReader.getText(BasicStreamReader.java:809)
at
org
.apache
.solr
.handler
.XmlUpdateRequestHandler.readDoc(XmlUpdateRequestHandler.java:327)
at
org
.apache
.solr
.handler
.XmlUpdateRequestHandler.processUpdate(XmlUpdateRequestHandler.java:
195)
at
org
.apache
.solr
.handler
.XmlUpdateRequestHandler
.handleRequestBody(XmlUpdateRequestHandler.java:123)
Before any CorruptIndexExceptions - could that be the root cause?
This exception looks like something new. I don't think this could
cause index corruption.
I'm not certain, but I think that stack trace is happening when Solr
is attempting to read/parse the incoming XML that your client is
sending it. The XML parser seems to feel it encountered an EOF. So
this looks like a client/server communication issue, I'm guessing.
Unfortunately the indices are large and contain confidential
information; is
there anything else I can do to identify where the problem is and why
CheckIndex isn't catching it?
Hmm, OK...
Could you post the full output of CheckIndex on the index?
Is there any chance you are allowing two Solr instances to run in the
same area? What's most important here is we get to the root cause of
this corruption. And, I'd like to explain why CheckIndex fails to
catch the "docs out of order" corruption, too.
Mike
