I think this issue is tot related to patch SOLR-1736 Here is the error I get ... Thank you for any help
[2010-03-02 19:07:26] [pool-3-thread-1] ERROR(ReplicationHandler.java:266) - SnapPull failed org.apache.solr.common.SolrException: Unable to download _7bre.fdt completely. Downloaded 0!=15591 at org.apache.solr.handler.SnapPuller$FileFetcher.cleanup(SnapPuller.java:1036) at org.apache.solr.handler.SnapPuller$FileFetcher.fetchFile(SnapPuller.java:916) 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:417) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:146) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:170) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) --- On Tue, 3/2/10, Matthieu Labour <matthieu_lab...@yahoo.com> wrote: From: Matthieu Labour <matthieu_lab...@yahoo.com> Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Tuesday, March 2, 2010, 11:23 AM Hi Paul Thank you for your amswer I did put all the directory structure on /raid ... /raid/solr_env/solr ... , /raid/solr_env/jetty ... And it still didn't work even after I applied patch SOLR-1736 I am investigating if this is because tempDir and data dir are not on the same partition matt --- On Mon, 3/1/10, Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com> wrote: From: Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com> Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Monday, March 1, 2010, 10:30 PM The data/index.20100226063400 dir is a temporary dir and isc reated in the same dir where the index dir is located. I'm wondering if the symlink is causing the problem. Why don't you set the data dir as /raid/data instead of /solr/data On Sat, Feb 27, 2010 at 12:13 AM, Matthieu Labour <matthieu_lab...@yahoo.com> wrote: > Hi > > I am still having issues with the replication and wonder if things are > working properly > > So I have 1 master and 1 slave > > On the slave, I deleted the data/index directory and > data/replication.properties file and restarted solr. > > When slave is pulling data from master, I can see that the size of data > directory is growing > > r...@slr8:/raid/data# du -sh > 3.7M . > r...@slr8:/raid/data# du -sh > 4.7M . > > and I can see that data/replication.properties file got created and also a > directory data/index.20100226063400 > > soon after index.20100226063400 disapears and the size of data/index is back > to 12K > > r...@slr8:/raid/data/index# du -sh > 12K . > > And when I look for the number of documents via the admin interface, I still > see 0 documents so I feel something is wrong > > One more thing, I have a symlink for /solr/data ---> /raid/data > > Thank you for your help ! > > matt > > > > > > > -- ----------------------------------------------------- Noble Paul | Systems Architect| AOL | http://aol.com
