Hi, We're looking forward to using Solr in a project. We're using a typical setup with one Master and a handful of Slaves. We're using the Master for writes and the Slaves for reads. Standard stuff.
Our concern is with downtime of the Master server. I read a few posts that touched on this topic but didn't find anything substantive. I've got a test setup in place that appears to work, but I'd like to get some feedback. Essentially, the plan is to add another Master server, so now we have M1 and M2. Both M1 and M2 are also configured to be slaves of each other. The plan is to put a load balancer in between the Slaves and the Master servers. This way, if M1 goes down, traffic will be routed to M2 automatically. Once M1 comes back online, we'll route traffic back to that server. Because M1 and M2 are replicating each other all updates are captured. To test this, I ran the following scenario. 1) Slave 1 (S1) is configured to use M2 as it's master. 2) We push an update to M2. 3) We restart S1, now pointing to M1. 4) We wait for M1 to sync from M2 5) We then sync S1 to M1. 6) Success! However... M1 and M2 generate snapshots every time they sync to each other, even if no new data was pushed to them from a Slave. We're concerned about this. Is this even a problem? Are we stuck in some infinte sync loop between the 2 Master machines? Will this degrade performance of the Master machines over time? Is there anything else I should know about this setup? Any insights, or alternative suggestions to this setup are quite welcome. Thanks, Erik -- View this message in context: http://www.nabble.com/Master-failover---seeking-comments-tp21614750p21614750.html Sent from the Solr - User mailing list archive at Nabble.com.
