In our current architecture, we use a staging core to perform full re-indexes while the live core continues to serve queries. After a full re-index we use the core admin to swap the live and stage index. Both the live and stage core are on the same solr instance.
In our new architecture we want to have the live core and stage core running on separate solr instances. Using core admin to swap is not longer possible so we use the replication command below to push the stage indexed to live index. http://search-stage9084/solr/replication?command=fetchindex&masterUrl=http://search-live:9084/solr/live/replication Is this operation guaranteed to be atomic? For example if replication fails halfway through, the old live index will still be good? Also during replication, will the live server continue to serve queries without performance penalty? -- View this message in context: http://lucene.472066.n3.nabble.com/Is-replication-an-atomic-operation-tp4026813.html Sent from the Solr - User mailing list archive at Nabble.com.
