I am currently looking at moving our Solr cluster to 4.2 and noticed a strange issue while testing today. Specifically the replica has a higher version than the master which is causing the index to not replicate. Because of this the replica has fewer documents than the master. What could cause this and how can I resolve it short of taking down the index and scping the right version in?
MASTER: Last Modified:about an hour ago Num Docs:164880 Max Doc:164880 Deleted Docs:0 Version:2387 Segment Count:23 REPLICA: Last Modified: about an hour ago Num Docs:164773 Max Doc:164773 Deleted Docs:0 Version:3001 Segment Count:30 in the replicas log it says this: INFO: Creating new http client, config:maxConnectionsPerHost=20&maxConnections=10000&connTimeout=30000&socketTimeout=30000&retry=false Apr 2, 2013 8:15:06 PM org.apache.solr.update.PeerSync sync INFO: PeerSync: core=dsc-shard5-core2 url=http://10.38.33.17:7577/solrSTART replicas=[ http://10.38.33.16:7575/solr/dsc-shard5-core1/] nUpdates=100 Apr 2, 2013 8:15:06 PM org.apache.solr.update.PeerSync handleVersions INFO: PeerSync: core=dsc-shard5-core2 url=http://10.38.33.17:7577/solr Received 100 versions from 10.38.33.16:7575/solr/dsc-shard5-core1/ Apr 2, 2013 8:15:06 PM org.apache.solr.update.PeerSync handleVersions INFO: PeerSync: core=dsc-shard5-core2 url=http://10.38.33.17:7577/solr Our versions are newer. ourLowThreshold=1431233788792274944 otherHigh=1431233789440294912 Apr 2, 2013 8:15:06 PM org.apache.solr.update.PeerSync sync INFO: PeerSync: core=dsc-shard5-core2 url=http://10.38.33.17:7577/solrDONE. sync succeeded which again seems to point that it thinks it has a newer version of the index so it aborts. This happened while having 10 threads indexing 10,000 items writing to a 6 shard (1 replica each) cluster. Any thoughts on this or what I should look for would be appreciated.
