I'm not entirely clear about your question. However, in replication, you should never commit docs directly to your slave, it will mess up the synchronisation of your indexes, and hence mess up your replication. If that's what you are proposing, don't do it!
Upayavira On Thu, Jul 25, 2013, at 08:29 PM, SolrLover wrote: > We are using SOLR 4.3.1 but not using solrcloud now. > > We currently support both push and pull indexing and we use softcommit > for > push indexing purpose. Now whenever we perform pull indexing (using > indexer > program) the changes made by the push indexing process (during indexing > time) might get lost hence trying to figure out a way to merge the > modified > documents.. > > I can implement a master and slave setup. I can initiate pull indexing in > master, slave will be accepting the documents pushed via queue. Now once > the > indexing in master is completed, I can replicate the index in slave. I > just > want to confirm, if the additional documents in slave will get deleted > during replication or the new data will get appended in slave? If not, is > there any other way to resolve this issue? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Can-we-use-replication-to-union-the-data-of-master-and-slave-tp4080425.html > Sent from the Solr - User mailing list archive at Nabble.com.
