Am Donnerstag, den 05.01.2012, 08:48 -0500 schrieb Erick Erickson: > Have you looked at deletionPolicy and maxCommitsToKeep?
Hm, but that are deletion policy parameters for the "running" index, how
much commit points should be kept - the internal ones from lucene:
#####################################################
<!-- configure deletion policy here-->
<deletionPolicy class="solr.SolrIndexDeletionPolicy">
<!-- Store only the commits with optimize.Non optimized commits
will get deleted by lucene when
the last IndexWriter/IndexReader using this commit point is
closed -->
<str name="keepOptimizedOnly">true</str>
<!--Maximum no: of commit points stored . Older ones will be
cleaned when they go out of scope-->
<str name="maxCommitsToKeep"></str>
<!-- max age of a stored commit-->
<str name="maxCommitAge"></str>
</deletionPolicy>
#####################################################
A rotated snapshot is everytime out-of-scope - its like a backup,
maxCommitsToKeep would not make any sense here, right?
Reading this: https://issues.apache.org/jira/browse/SOLR-617 it sounds
like different use case.
Are there really meant to be used for rotation the snapshot directories,
reading the comments it does not sound to be what i am looking for, am i
right?
regards
Torsten
>
> Best
> Erick
>
> On Tue, Jan 3, 2012 at 8:32 AM, Torsten Krah
> <tk...@fachschaft.imn.htwk-leipzig.de> wrote:
> > Hi,
> >
> > i am taking snapshots of my master index after optimize calls (run each
> > day once), to get a clean backup of the index.
> > Is there a parameter to tell the replication handler how many snapshots
> > to keep and the rest should be deleted? Or must i use a custom script
> > via cron?
> >
> > regards
> >
> > Torsten
smime.p7s
Description: S/MIME cryptographic signature
