Hi,
I uploaded the log to drive.
https://drive.google.com/file/d/0B0GR0M-lL5QHX1B2a2NZZXh3a1E/view?usp=sharing



Regards,
Moshe Recanati
SVP Engineering
Office + 972-73-2617564
Mobile  + 972-52-6194481
Skype    :  recanati
[KMS2]<http://finance.yahoo.com/news/kms-lighthouse-named-gartner-cool-121000184.html>
More at:  www.kmslh.com<http://www.kmslh.com/> | 
LinkedIn<http://www.linkedin.com/company/kms-lighthouse> | 
FB<https://www.facebook.com/pages/KMS-lighthouse/123774257810917>


From: Moshe Recanati [mailto:mos...@kmslh.com]
Sent: Wednesday, April 01, 2015 5:22 PM
To: solr-user@lucene.apache.org
Subject: Error while reading index

Hi,
We're running on production environment with Solr 4.7.1 master and slave with 
replication every 1 minute.
During regular activity and index delta build we got the following error:
ERROR - 2015-03-30 04:06:12.318; java.lang.RuntimeException: [was class 
java.net.SocketException] Connection reset
                at 
com.ctc.wstx.util.ExceptionUtil.throwRuntimeException(ExceptionUtil.java:18)
                at 
com.ctc.wstx.sr.StreamScanner.throwLazyError(StreamScanner.java:731)

After additional 2 minutes we got the following error:
ERROR - 2015-03-30 04:07:39.875; Unable to get file names for indexCommit 
generation: 638
java.io.FileNotFoundException: _tu.fdt
                at 
org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:261)
                at 
org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:178)

And since than Solr wasn't recover until we did full rebuild of all documents.
Detailed log attached.

Let me know if you familiar with such issue.
And what can create such issue that prevent from recovery and requires rebuild 
index. This is major issue for us.

Thank you in advance,


Regards,
Moshe Recanati
SVP Engineering
Office + 972-73-2617564
Mobile  + 972-52-6194481
Skype    :  recanati
[KMS2]<http://finance.yahoo.com/news/kms-lighthouse-named-gartner-cool-121000184.html>
More at:  www.kmslh.com<http://www.kmslh.com/> | 
LinkedIn<http://www.linkedin.com/company/kms-lighthouse> | 
FB<https://www.facebook.com/pages/KMS-lighthouse/123774257810917>


Reply via email to