Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 39910 invoked from network); 16 Nov 2008 13:40:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Nov 2008 13:40:16 -0000 Received: (qmail 14044 invoked by uid 500); 16 Nov 2008 13:40:16 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 14015 invoked by uid 500); 16 Nov 2008 13:40:16 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 14004 invoked by uid 99); 16 Nov 2008 13:40:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Nov 2008 05:40:16 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of evalsinca@hotmail.com designates 65.54.246.214 as permitted sender) Received: from [65.54.246.214] (HELO bay0-omc3-s14.bay0.hotmail.com) (65.54.246.214) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Nov 2008 13:38:53 +0000 Received: from BAY123-DS3 ([207.46.11.30]) by bay0-omc3-s14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 16 Nov 2008 05:39:37 -0800 X-Originating-IP: [24.6.173.219] X-Originating-Email: [evalsinca@hotmail.com] Message-ID: From: "William Pierce" In-Reply-To: <5e76b0ad0811152340l5b1f4e0dybbbc83e4dc224d63@mail.gmail.com> To: References: <5e76b0ad0811152340l5b1f4e0dybbbc83e4dc224d63@mail.gmail.com> Subject: Re: Fatal exception in solr 1.3+ replication Date: Sun, 16 Nov 2008 05:39:35 -0800 MIME-Version: 1.0 X-Unsent: 1 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 X-OriginalArrivalTime: 16 Nov 2008 13:39:37.0014 (UTC) FILETIME=[C46F9560:01C947F0] X-Virus-Checked: Checked by ClamAV on apache.org Not easily no...It has occurred twice on my machine but what triggers it I do not know. Mark Miller has provided some explanations for what may be going on in Lucene that may be causing this....Cf. his last email.... - Bill -------------------------------------------------- From: "Noble Paul ??????? ??????" Sent: Saturday, November 15, 2008 11:40 PM To: Subject: Re: Fatal exception in solr 1.3+ replication > Is this issue visible for consistently ? I mean are you able to > reproduce this easily? > > On Fri, Nov 14, 2008 at 11:15 PM, 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 > > > > -- > --Noble Paul >