has master updated index during replication? this could occur when it failed to download any file becuase network problem. 209715200!=583644834 means the size of the file slave fetched is 583644834 but it only download 209715200 bytes. maybe the connection is time out.
2011/2/16 Markus Jelsma <markus.jel...@openindex.io>: > Hi, > > There are a couple of Solr 1.4.1 slaves, all doing the same. Pulling some > snaps, handling some queries, nothing exciting. But can anyone explain a > sudden nightly occurence of this error? > > 2011-02-16 01:23:04,527 ERROR [solr.handler.ReplicationHandler] - [pool-238- > thread-1] - : SnapPull failed > org.apache.solr.common.SolrException: Unable to download _gv.frq completely. > Downloaded 209715200!=583644834 > at > org.apache.solr.handler.SnapPuller$FileFetcher.cleanup(SnapPuller.java:1026) > at > org.apache.solr.handler.SnapPuller$FileFetcher.fetchFile(SnapPuller.java:906) > at > org.apache.solr.handler.SnapPuller.downloadIndexFiles(SnapPuller.java:541) > at > org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:294) > at > org.apache.solr.handler.ReplicationHandler.doFetch(ReplicationHandler.java:264) > at org.apache.solr.handler.SnapPuller$1.run(SnapPuller.java:159) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > All i know is that it was unable to download but the reason eludes me. > Sometimes, a machine rolls out many of these errors and increasing the index > size because it can't handle the already downloaded data. > > Cheers, > -- > Markus Jelsma - CTO - Openindex > http://www.linkedin.com/in/markus17 > 050-8536620 / 06-50258350 >
