Thanks Shawn, for reminding CloudSolrServer, yes I have moved to SolrCloud.
I agree that repeater is a slave and acts as master for other slaves. But still it's a master and logically it has to obey the what master suppose to obey. if 2 servers are master that means writing can be done on both. If I setup replication between 2 servers and configure both as repeater, than both can act master and slave for each other. Therefore writing can be done on both. Rgds AJ > On Jun 6, 2015, at 1:26 AM, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 6/5/2015 1:38 PM, Amit Jha wrote: >> Thanks Eric, what about document is committed to master?Then document should >> be visible from master. Is that correct? >> >> I was using replication with repeater mode because LBHttpSolrServer can send >> write request to any of the Solr server, and that Solr should index the >> document because it a master. we have a polling interval of 2 sec. After >> polling interval slave can poll the data. It is worth to mention here is >> application request the commit command. >> >> If document is committed to master and a search request coming to the same >> master then document should be retrieved. Irrespective of replication >> because master doesn't know who the slave are? >> >> In repeater mode document can be indexed on both the Solr instance. Is that >> understanding correct? >> >> Also why you say that commit is inappropriate? > > If you are not using SolrCloud, then you must index to the master > *ONLY*. A repeater does not enable two-way replication. A repeater is > a slave that is also a master for additional slaves. Master-slave > replication is *only* one-way - from the master to slaves, and if any of > those slaves are repeaters, from there to additional slaves. > > SolrCloud is probably a far better choice for your setup, especially if > you are using the SolrJ client. You mentioned LBHttpSolrServer, which > is why I am thinking you're using SolrJ. > > With a proper configuration on your collection, SolrCloud lets you index > to any machine in the cloud and the data will end up exactly where it > needs to go. If you use CloudSolrServer/CloudSolrClient and a very > recent Solr/SolrJ version, the data will be sent directly to the correct > instance for best performance. > > Thanks, > Shawn >
