If I understand you right, replication of data has 0 downtime, it just works and the data flows through from master to slaves. If you want, you can configure the replication to replicate configuration files across the cluster (although to me my deploy script does this). I'd recommend tweaking the warmers so that you don't get latency spikes due to cold caches during the replications.
Not being well versed in the latest Solr features (I'm a bit behind here), I don't know if you can reload the cores on demand to indicate the latest configurations or not but in my environment, I have a rolling restart script that bounces a set of servers when the schema/solrconfig changes. HTH Amit On Mon, Sep 10, 2012 at 11:10 PM, Abhishek tiwari <[email protected]> wrote: > HI All, > > am having 1 master and 3 slave solr server.(verson 3.6) > What kind of replication policy should i adopt with zero down time & no > data loss . > > 1) when we do some configuration and schema changes on the solr server .
