Replication is basically a background file transfer, your slave shouldn't
notice.
But what your slave will notice is two things:
1> after replication if your first few queries are slow, you need to
autowarm your caches.
2> you will see some memory footprint increase while autowarming
is going on
But by and large, your slave won't notice the replication itself and the
other stuff is configurable via autowarming parameters in your various
caches and newSearcher/firstSearcher
Best
Erick
On Mon, Dec 5, 2011 at 5:44 AM, roySolr <royrutten1...@gmail.com> wrote:
> Hello,
>
> I have one solr instance and i'm very happy with that. Now we have multiple
> daily updates
> and is see the response time is slower when doing a update. I think i need
> some master slave replication. Now my question is: Is a slave slower when
> there is an replication running from master to slave? Is there any downtime
> when switching from old to new data?
>
> I only need 1 slave for performace but when replication makes it slower i
> probably need 2.
>
> Thanks
> Roy
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Replication-downtime-master-slave-tp3561031p3561031.html
> Sent from the Solr - User mailing list archive at Nabble.com.
