You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2006/04/11 21:09:31 UTC
[Solr Wiki] Update of "SolrOperationsTools" by BillAu
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by BillAu:
http://wiki.apache.org/solr/SolrOperationsTools
New page:
[[TableOfContents]]
== basic Solr scripts ==
These scripts are used to manage the index data on the Solr server:
||'''Name'''||'''Description'''||
||'''abc'''||Atomic Backup post-Commit tells the Solr server to perform a commit. A snapshot of the index directory is made after the commit if the Solr server is configured to do so (by enabling the '''postCommit''' event listener in '''solr/conf/solrconfig.xml'''). A backup of the most recent snapshot directory is then made if the commit is successful. Backup directories are named '''backup.''yyyymmddHHMMSS''''' where ''yyyymmddHHMMSS'' is the timestamp of when the snaphot was taken.||
||'''abo'''||Atomic Backup post-Optimize tells the Solr server to perform an optimize. A snapshot of the index directory is made after the optimize if the Solr server is configured to do so (by enabling the '''postCommit''' or '''postOptimize''' event listener in '''solr/conf/solrconfig.xml'''). A backup of the most recent snapshot directory is then made if the optimize is successful. Backup directories are named '''backup.''yyyymmddHHMMSS''''' where ''yyyymmddHHMMSS'' is the timestamp of when the snaphot was taken.||
||'''backup'''||Backup the index directory using hard links. Backup directories are named '''backup.''yyyymmddHHMMSS''''' where ''yyyymmddHHMMSS'' is the timestamp of when the backup was taken.||
||'''backupcleaner'''||Runs as a cron job to remove backups more than a configurable number of days old or all backups except for the most recent n number of backups. Also can be run manually.||
||'''commit'''||Issues a commit to the Solr server. This will also causes a snapshot to be created if the Solr server is configured to take a snapshot after a commit (by enabling the '''postCommit''' event listener in '''solr/conf/solrconfig.xml''').||
||'''optimize'''||Issues an optimize to the Solr server. '''Note''': Optimization may take up to several minutes depending on the size of the index. This will also causes a snapshot to be created if the Solr server is configured to take a snapshot after an optimzie (by enabling the '''postCommit''' or '''postOptimize''' event listener in '''solr/conf/solrconfig.xml''').||
||'''readercycle'''||tells the Solr server to close its current reader and open a new one. This has the effect of making any recent updates and deletions visible to the new reader.||
== Solr collection distribution scripts ==
These scripts are run on the master and slave Solr servers to
* create and deliver snapshots from the master to the slave(s)
* install snapshot on the slave(s)
* report distribution statistics and status from slave(s) to master
They are documented in SolrCollectionDistributionScripts.