We have the following high-level solr setup: region a) 1 solr master + 3 slaves region b) 1 solr repeater (pointing to master in region a) + 3 slaves
In region (a) Replication takes about 2 min from the master to the 3 slaves. Due to our network topology, replication from the master to the repeater takes about 15 min after which, it takes another 2 min for the replication to occur between the repeater and the slaves in region (b), so the slaves in region (b) are always 15 min behind the slaves in region (a) which is a problem because all slaves are behind a latency-based route53 record. Clients are noticing the difference because they are getting inconsistent data during those 15 min. I would like to solve this inconsistency. Is there a way to make the faster slaves in region (a) wait for all slaves in region (b) to complete replication and then have all 6 slaves switch to the new index simultaneously? if not, what is the alternative solution to this problem? - Csongor Note: We are on solr 3.5 (old, yes I know...)
