Yes. This is going to hurt you a lot. The intent of M/S is that you should be indexing to one, and only one machine, the master. All slaves pull their indexes from the master. Frankly I don't know quite what will happen in the configuration you're talking about. I strongly recommend you do not do this.
HA is not at all difficult in a M/S situation. Just configure as many slaves as you need, all pointing to the same master. Then have your LB point to the slaves. And have your indexing process(es) point to the master and only the master. Bringing up a new slave is as simple as configuring a new machine, pointing it to the master, waiting for replication to complete then letting the LB know about the new machine. What you don't get is fail-over if the master goes down. You can promote one of the slaves to be a master but you have to put a mechanism in place that allows you to "catch up" that index, which is often just re-indexing everything from before the master went down to the new master. You said you don't want to go to SolrCloud, and that's up to you. But automatic, robust HA/DR is hard. If your goal is to have a fault-tolerant, automated recovery system I really urge you to reconsider SolrCloud. The _point_ of SolrCloud is exactly that. If you try to re-invent that process you'll be in for a lot of work. There, rant finished :) Erick On Tue, Nov 26, 2013 at 1:47 PM, kondamudims <kondamud...@gmail.com> wrote: > We are trying to setup solr Master Slave repeater model, where we will have > two solr servers say S1 and S2 and a Load balancer LB to route all the > requests to either S1 or S2. S1 and S2 acts as both Master and > Slave(Repeater). In both the solr server configurations, in the > solrconfig.xml file for master url property if we provide Load balancer > host-name and port number then at any point there will be a self polling, > i.e. if LB is configured in such a way that all its requests will be routed > to S1, then while polling S1-->LB-->S1 and S2-->LB-->S1. Do you see any > issue with self polling(S1-->LB-->). We are mainly trying to achieve High > availability as we don't want to use Solr Cloud. Thanks in advance > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SOLR-Master-Slave-Repeater-with-Load-balancer-tp4103363.html > Sent from the Solr - User mailing list archive at Nabble.com. >
