Renamed it on the Slave server.

The slave does create a new index.xxxxxxxxxx directory to store temporary
files, but they are much smaller than the full catalog size. These files
then get copied/merged to the "index" directory, and the index.xxxxxxxxxx
directory is deleted at the end. I end up with just the "index" directory
after replication is complete.

I'm using Tomcat/Solr 4.1

-----Original Message-----
From: adityab [mailto:aditya_ba...@yahoo.com] 
Sent: Wednesday, February 27, 2013 12:22 PM
To: solr-user@lucene.apache.org
Subject: RE: Solr 4.1 Master -> Slave Replication Issues and Solr 4.2

@Hung,
Did you rename the index directory on master or on Slave?
I tried this but didn't work for me. :( with every commit the slave creates
a new index.xxxxxxxxx directory and download the complete index from master.
My setup is JBoss7.1.1 with Solr 4.1 


thanks
Aditya



--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-1-Master-Slave-Replication-Issues-
and-Solr-4-2-tp4043403p4043426.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to