Re: Fatal exception in solr 1.3+ replication

Fri, 14 Nov 2008 20:44:18 -0800

Hey William, sorry about the trouble. I have to look at this further, but I think the issue is fixed if you grab the latest trunk build. Solr-465 should inadvertently fix things - before that patch, a deprecated constructor for solrsearcher was being called - this constructor caused the underlying IndexReader to close its own Directory, and since IndexReaders are reopened, we don't want that. 

Mark Miller wrote:
Looks like there might be an issue with the reopen - I'm not seeing what it could be offhand though. Have to find what could be closing a Directory unexpectedly...I'll try to take a further look over the weekend. 

- Mark

William Pierce wrote:

Folks:


I am using the nightly build of 1.3 as of Oct 23 so as to use the 
replication handler.   I am running on windows 2003 server with 
tomcat 6.0.14.   Everything was running fine until I noticed that 
certain updated records were not showing up on the slave.  Further 
investigation showed me that the failures have indeed been occurring 
since early this morning with a fatal exception....here is a segment 
of the tomcat log:

  INFO: Total time taken for download : 0 secs

  Nov 14, 2008 5:34:24 AM org.apache.solr.handler.SnapPuller 
fetchLatestIndex

  INFO: Conf files are not downloaded or are in sync

  Nov 14, 2008 5:34:24 AM org.apache.solr.update.DirectUpdateHandler2 
commit

  INFO: start commit(optimize=false,waitFlush=true,waitSearcher=true)

  Nov 14, 2008 5:34:24 AM org.apache.solr.handler.ReplicationHandler 
doSnapPull
  SEVERE: SnapPull failed   org.apache.solr.common.SolrException: 
Snappull failed :    at 
org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:278)
   at 
org.apache.solr.handler.ReplicationHandler.doSnapPull(ReplicationHandler.java:208) 


   at org.apache.solr.handler.SnapPuller$1.run(SnapPuller.java:121)

   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:885) 

   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) 


   at java.lang.Thread.run(Thread.java:619)

  Caused by: java.lang.RuntimeException: 
org.apache.lucene.store.AlreadyClosedException: this Directory is closed

   at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1037)

   at 
org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:350) 


   at org.apache.solr.handler.SnapPuller.doCommit(SnapPuller.java:353)

   at 
org.apache.solr.handler.SnapPuller.fetchLatestIndex(SnapPuller.java:265)

   ... 11 more

  Caused by: org.apache.lucene.store.AlreadyClosedException: this 
Directory is closed

   at org.apache.lucene.store.Directory.ensureOpen(Directory.java:220)
   at org.apache.lucene.store.FSDirectory.list(FSDirectory.java:320)

   at 
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:533) 

   at 
org.apache.lucene.index.SegmentInfos.readCurrentVersion(SegmentInfos.java:366) 

   at 
org.apache.lucene.index.DirectoryIndexReader.isCurrent(DirectoryIndexReader.java:188) 

   at 
org.apache.lucene.index.DirectoryIndexReader.reopen(DirectoryIndexReader.java:124) 


   at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1016)
   ... 14 more

  Nov 14, 2008 5:38:52 AM org.apache.solr.update.DirectUpdateHandler2 
commit


Any ideas, anyone?

-- Bill

  


























					Reply via email to