lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SolrReplication" by JamesDyer
Date Tue, 28 Feb 2012 15:58:08 GMT
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 JamesDyer:
http://wiki.apache.org/solr/SolrReplication?action=diff&rev1=79&rev2=80

          <!--The default value of reservation is 10 secs.See the documentation below .
Normally , you should not need to specify this -->
          <str name="commitReserveDuration">00:00:10</str>
      </lst>
+     <!-- keep only 1 backup.  Using this parameter precludes using the "numberToKeep"
request parameter. -->
+     <str name="maxNumberOfBackups">1</str> 
  </requestHandler>
  }}}
  '''Note:'''
@@ -214, +216 @@

   * Abort copying index from master to slave command: http://slave_host:port/solr/replication?command=abortfetch
   * Create a backup on master if there are committed index data in the server, otherwise
do nothing. This is useful to take periodic backups. Command: http://master_host:port/solr/replication?command=backup.
 
    * Can also provide a location parameter (i.e. &location=/foo/bar), which is the directory
to write the backup to on disk.  
-   * Specify parameter "numberToKeep" to indicate how many backups to retain (including this
one).  Older backups will be automatically deleted. (i.e. &numberToKeep=2) [[Solr3.5]]
[[Solr4.0]] [[https://issues.apache.org/jira/browse/SOLR-2578|SOLR-2578]]
+   * Specify parameter "numberToKeep" to indicate how many backups to retain (including this
one).  Older backups will be automatically deleted. (i.e. &numberToKeep=2) [[Solr3.5]]
[[Solr4.0]]
+     (note:  this parameter cannot be specified if "maxNumberOfBackups" was specified in
the configuration. [[Solr3.6]] [[Solr4.0]] )
+ [[https://issues.apache.org/jira/browse/SOLR-2578|SOLR-2578]]
   * Force a fetchindex on slave from master command: http://slave_host:port/solr/replication?command=fetchindex
    * It is possible to pass on extra attribute 'masterUrl' or other attributes like 'compression'
(or any other parameter which is specified in the {{{<lst name="slave">}}} tag) to do
a one time replication from a master. This obviates the need for hardcoding the master in
the slave.
   * Disable polling for changes from slave command: http://slave_host:port/solr/replication?command=disablepoll

Mime
View raw message