Cannot finish recovery due to always met ReplicationHandler SnapPull failed: Unable to download xxx.fdt completely

I have 2 solr nodes(solr1 and solr2) in a SolrCloud. After some issue happened, solr2 are in recovering state. The peersync cannot finish in about 15 min, so it turn to snappull. But when it's doing snap pull, it always met this issue below. Meanwhile, there are still update requests sent to

Re: Cannot finish recovery due to always met ReplicationHandler SnapPull failed: Unable to download xxx.fdt completely

Why does PeerSync take so much time? Are these two nodes in different data centers or are they connected by a slow link? On Thu, Aug 7, 2014 at 12:41 PM, forest_soup tanglin0...@gmail.com wrote: I have 2 solr nodes(solr1 and solr2) in a SolrCloud. After some issue happened, solr2 are in

Re: Cannot finish recovery due to always met ReplicationHandler SnapPull failed: Unable to download xxx.fdt completely

Thanks. My env is 2 VM with good network condition. So not sure why it is happened. We are trying to reproduce it. The peersync fail log is : 2014年7月25日 上午6:30:48 WARN SnapPuller Error in fetching packets java.io.EOFException at

Re: Cannot finish recovery due to always met ReplicationHandler SnapPull failed: Unable to download xxx.fdt completely

I have opened one JIRA for it: https://issues.apache.org/jira/browse/SOLR-6333 -- View this message in context: http://lucene.472066.n3.nabble.com/Cannot-finish-recovery-due-to-always-met-ReplicationHandler-SnapPull-failed-Unable-to-download-xxx-fy-tp4151611p4151631.html Sent from the Solr -