Here is briefly what is happening:

I have a simple SolrCloud environment for test purposes, running with a
zookeeper ensemble, not the ones embedded in Solr.

I have 3 instances in the cloud, all of them are using RAMDirectory (which
is enabled by new Solr release to use with cloud)

After running zookeepers and connecting my solrs to them, the cloud is up
without any errors or problems. Then I have started indexing (which is much
slower than a single instance, i will open a topic about it too) and
everything is okay once again, all of the nodes get the sync'ed data from
the leader node. 

After that I have killed one Solr instance. then I have restarted it and in
the logs it keeps showing me these errors:

SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
Server at http://myhost:8995/solr/mycore returned non ok status:500,
message:Server Error
        at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:372)
        at
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:181)
        at
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)
        at
org.apache.solr.cloud.RecoveryStrategy.commitOnLeader(RecoveryStrategy.java:182)
        at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:134)
        at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:407)
        at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:222)
.
.
.
.
.

Nov 27, 2012 11:49:04 AM
org.apache.solr.handler.SnapPuller$DirectoryFileFetcher fetchPackets
WARNING: Error in fetching packets 
java.io.EOFException
        at
org.apache.solr.common.util.FastInputStream.readFully(FastInputStream.java:151)
        at
org.apache.solr.common.util.FastInputStream.readFully(FastInputStream.java:144)
        at
org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.fetchPackets(SnapPuller.java:1143)
        at
org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.fetchFile(SnapPuller.java:1107)
        at
org.apache.solr.handler.SnapPuller.downloadIndexFiles(SnapPuller.java:716)
        at 
org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:387)
        at
org.apache.solr.handler.ReplicationHandler.doFetch(ReplicationHandler.java:273)
        at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:152)
        at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:407)
        at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:222)
.
.
.
.
.
SEVERE: SnapPull failed :org.apache.solr.common.SolrException: Unable to
download _41y.fdt completely. Downloaded 3145728!=3243906
        at
org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.cleanup(SnapPuller.java:1237)
        at
org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.fetchFile(SnapPuller.java:1118)
        at
org.apache.solr.handler.SnapPuller.downloadIndexFiles(SnapPuller.java:716)
        at 
org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:387)
        at
org.apache.solr.handler.ReplicationHandler.doFetch(ReplicationHandler.java:273)
        at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:152)
        at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:407)
        at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:222)
SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
Replication for recovery failed.
        at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:155)
        at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:407)
        at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:222)



can anyone explain why i am getting this error? 












-----
Zeki ama calismiyor... Calissa yapar...
--
View this message in context: 
http://lucene.472066.n3.nabble.com/SolrCloud-5x-Errors-while-recovering-tp4022542.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to