Thanks Shawn, We do have repeaters setup to replicate index to the 8 Slaves. We update documents to Master every 2hrs in a batch process. When on hard commit is replicated to repeaters and then to slaves. The concern is that during heavy traffic when slaves are busy serving request, when a new index is available on repeater all slaves start replicating at the same time. And that's when we see the spike on entire cluster. In a single cluster we have 1 Master, 2 Repeaters, 8 slaves. We have currently implemented a cron job which performs staggered replication so not all slaves spike at same time and the cluster is in a state to serve traffic.
-- View this message in context: http://lucene.472066.n3.nabble.com/Staggered-Replication-In-Solr-tp4076659p4076888.html Sent from the Solr - User mailing list archive at Nabble.com.
