Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "SolrReplication" page has been changed by FredDrake. The comment on this change is: fix typos. http://wiki.apache.org/solr/SolrReplication?action=diff&rev1=65&rev2=66 -------------------------------------------------- = How does it work ? = - This feature relies on the [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexDeletionPolicy.html|IndexDeletionPolicy]] feature of Lucene. Through this API, Lucene exposes [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexCommit.html|IndexCommits]] as callbacks for each commit/optimize .An [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexCommit.html|IndexCommit]] exposes the files associated with each commit. This enables us to identify the files that need to be replicated . + This feature relies on the [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexDeletionPolicy.html|IndexDeletionPolicy]] feature of Lucene. Through this API, Lucene exposes [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexCommit.html|IndexCommits]] as callbacks for each commit/optimize. An [[http://hudson.zones.apache.org/hudson/job/Lucene-trunk/javadoc/core/org/apache/lucene/index/IndexCommit.html|IndexCommit]] exposes the files associated with each commit. This enables us to identify the files that need to be replicated. - - True to the tradition of Solr, all operations are performed over a REST API. The !ReplicationHandler exposes a REST API for all the operations it support. + True to the tradition of Solr, all operations are performed over a REST API. The !ReplicationHandler exposes a REST API for all the operations it supports. == What happens when I commit or optimize? == - When a commit/optimize is done on master , !ReplicationHandler reads the list of file names which are associated with each commit point.This relies on the 'replicateAfter' parameter in the configuration to decide when these file names are to be fetched and stored from Lucene. + When a commit/optimize is done on master, !ReplicationHandler reads the list of file names which are associated with each commit point. This relies on the 'replicateAfter' parameter in the configuration to decide when these file names are to be fetched and stored from Lucene. == How does the slave replicate ? ==
