You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Eric Tang <er...@gmail.com> on 2011/12/20 05:18:01 UTC

Replication Index Fetch error

Hi,

I'm running a master-slave setup, both on 3.2, and am having an issue with
the slave node.

I promoted my old slave node to master, took down the old master, and made
it into a slave.  Now I can't get the new slave to fetch index.  There are
a little over a million documents in the index.


SEVERE: SnapPull failed
org.apache.solr.common.SolrException: Index fetch failed :
at org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:331)
 at
org.apache.solr.handler.ReplicationHandler.doFetch(ReplicationHandler.java:267)
at org.apache.solr.handler.SnapPuller$1.run(SnapPuller.java:159)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.RuntimeException:
org.apache.lucene.index.CorruptIndexException: unrecognized format -3 in
file "_17rqr.fnm"
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1099)
 at
org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:425)
at org.apache.solr.handler.SnapPuller.doCommit(SnapPuller.java:470)
 at org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:321)
... 10 more
Caused by: org.apache.lucene.index.CorruptIndexException: unrecognized
format -3 in file "_17rqr.fnm"
at org.apache.lucene.index.FieldInfos.read(FieldInfos.java:351)
 at org.apache.lucene.index.FieldInfos.<init>(FieldInfos.java:71)
at
org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:72)
 at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:114)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:92)
 at org.apache.lucene.index.DirectoryReader.<init>(DirectoryReader.java:235)
at
org.apache.lucene.index.ReadOnlyDirectoryReader.<init>(ReadOnlyDirectoryReader.java:34)
 at
org.apache.lucene.index.DirectoryReader.doReopen(DirectoryReader.java:484)
at
org.apache.lucene.index.DirectoryReader.access$000(DirectoryReader.java:45)
 at
org.apache.lucene.index.DirectoryReader$2.doBody(DirectoryReader.java:476)
at
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:750)
 at
org.apache.lucene.index.DirectoryReader.doReopenNoWriter(DirectoryReader.java:471)
at
org.apache.lucene.index.DirectoryReader.doReopen(DirectoryReader.java:429)
 at org.apache.lucene.index.DirectoryReader.reopen(DirectoryReader.java:392)
at org.apache.solr.search.SolrIndexReader.reopen(SolrIndexReader.java:414)
 at org.apache.solr.search.SolrIndexReader.reopen(SolrIndexReader.java:425)
at org.apache.solr.search.SolrIndexReader.reopen(SolrIndexReader.java:35)
 at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1080)

Re: Replication Index Fetch error

Posted by Eric Tang <er...@gmail.com>.
That did it.  I was running 3.3 on one and 3.4 on another.

Thanks!

Eric

On Mon, Dec 19, 2011 at 11:49 PM, Michael Ryan <mr...@moreover.com> wrote:

> According to http://lucene.apache.org/java/3_4_0/fileformats.html, the
> FNMVersion changed from -2 to -3 in Lucene 3.4. Is it possible that the new
> master is actually running 3.4, and the new slave is running 3.2? (This is
> just a wild guess.)
>
> -Michael
>

RE: Replication Index Fetch error

Posted by Michael Ryan <mr...@moreover.com>.
According to http://lucene.apache.org/java/3_4_0/fileformats.html, the FNMVersion changed from -2 to -3 in Lucene 3.4. Is it possible that the new master is actually running 3.4, and the new slave is running 3.2? (This is just a wild guess.)

-Michael