May be the info about index version is pulled from the repeaters "data/replication.properties" file and the content of that file is wrong. Had something similar and only solution for me was deleting the replication.properties file. But no guarantee about this.
Actually the replication is pretty much messed up in solr4.1. Have seen about 6 or 7 erroneous combinations with replication that were leading to some kind of problems. My problem is I can't reproduce it continously to use a debugger :-( Positive point is, if something goes wrong it goes wrong on all slaves. Some kind of continuity :-) While writing this I just found a new combination. - master had clean index (everything committed, and optimized) and was successfully replicated to all slaves - master has added a few docs and committed - master was replicated to all slaves - all slaves have same generation and version as master but: - all slaves have now no index directory anymore. They only have an index.xxxxxxxxx directory and an additional index.properties file. I already knew that something would go wrong when I started replication and saw that the slaves pulled the whole index (again) from the master and not only the files with added docs. Under this circumstances with replication I would not even dream about using SolrCloud. Regards Bernd Am 27.02.2013 08:50, schrieb raulgrande83: > I'm now having a different problem. In my master-repeater-2slaves > architecture I have these generations versions: > Master: 29147 > Repeater: 29147 > Slaves: 29037 > > When I go to slaves logs it shows "Slave in sync with master". That is > apparently because if I do > http://localhost:17045/solr/replication?command=indexversion (my repeater's > replication URL) the response is: > <long name="generation">29037</long> > > Why this URL is returning an old index version? Any solutions to this? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Slaves-always-replicate-entire-index-Index-versions-tp4041256p4043314.html > Sent from the Solr - User mailing list archive at Nabble.com. >
