We have three dedicated servers for solr, two for slaves and one for master, all with linux/debian packages installed.
I understand that replication does always copies over the index in an exact form as in master index directory (or it is supposed to do that at least), and if the master index was optimized after indexing, one doesn't need to run an optimize call again on master to optimize the slave's index. But in our case thats what fixed it and I agree it is even more confusing now :s Another problem is, we are serving live services using slave nodes, so I dont want to effect the live search, while playing with slave nodes' indices. We will be running the indexing on master node today over the night. Lets see if it does it again. -- View this message in context: http://lucene.472066.n3.nabble.com/slave-index-is-bigger-than-master-index-tp996329p998750.html Sent from the Solr - User mailing list archive at Nabble.com.
