Thanks Daniel.
So, if I understand correctly the below exception is almost always
caused because of merging segments ? Though I see different file names
(for e.g download_av3.fdt in this case) in the exception messages
[explicit-fetchindex-cmd] ERROR
org.apache.solr.handler.ReplicationHandler- SnapPull failed
:org.apache.solr.common.SolrException: Unable to download _av3.fdt
completely . Downloaded 0!=497037
Thanks,
Anand
On 1/3/2014 11:04 PM, Daniel Collins wrote:
We see this a lot as well, my understanding is that recovery asks the
leader for a list of the files that it should download, then it downloads
them. But if the leader has been merging segments whilst this is going on
(recovery is taking a reasonable period of time and you have an NRT system
where commits/merges are reasonably frequent), then the segments might
disappear during this recovery period, hence the replica can't download
them.
So its an error, but something the system can recover from, since it will
re-recover, which should pick up a (larger) segment next time, which is
less likely to be removed whilst recovery is going on.
On 3 January 2014 05:32, anand chandak <anand.chan...@oracle.com> wrote:
Hi,
I am hitting this error on replication, can somebody please tell me what's
wrong here and what can be done to correct this error :
[explicit-fetchindex-cmd] ERROR org.apache.solr.handler.ReplicationHandler-
SnapPull failed :org.apache.solr.common.SolrException: Unable to download
_av3.fdt completely . Downloaded 0!=497037
2 at org.apache.solr.handler.SnapPuller$
DirectoryFileFetcher.cleanup(SnapPuller.java:1268)
3 at org.apache.solr.handler.SnapPuller$DirectoryFileFetcher.
fetchFile(SnapPuller.java:1148)
4 at org.apache.solr.handler.SnapPuller.downloadIndexFiles(
SnapPuller.java:743)
5 at org.apache.solr.handler.SnapPuller.fetchLatestIndex(
SnapPuller.java:407)
6 at org.apache.solr.handler.ReplicationHandler.doFetch(
ReplicationHandler.java:319)
7 at org.apache.solr.handler.ReplicationHandler$1.run(
ReplicationHandler.java:220)
Thanks,
Anand
