environment: solr 3.5

hello all,

i have a question on this jira -
https://issues.apache.org/jira/browse/SOLR-3361

the jira states that, "with "backupAfter"=commit, the backups do not get
cleaned up"

however - we are noticing this same issue in our environment, when using
optimize.

can someone confirm that this bug applies to "optimze" as well?

thank you

example:
      <str name="backupAfter">optimize</str>
--
View this message in context: http://lucene.472066.n3.nabble.com/maxNumberOfBackups-does-not-cleanup-jira-3361-tp3994156.html
Sent from the Solr - User mailing list archive at Nabble.com.

I'm also certain that it would apply to both "oncommit" and "onoptimize".

James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
-----Original Message-----
From: geeky2 [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2012 8:48 AM
To: [EMAIL PROTECTED]
Subject: maxNumberOfBackups does not cleanup - jira 3361
environment: solr 3.5

hello all,

i have a question on this jira -
https://issues.apache.org/jira/browse/SOLR-3361

the jira states that, "with "backupAfter"=commit, the backups do not get
cleaned up"

however - we are noticing this same issue in our environment, when using
optimize.

can someone confirm that this bug applies to "optimze" as well?

thank you

example:
      <str name="backupAfter">optimize</str>
--
View this message in context: http://lucene.472066.n3.nabble.com/maxNumberOfBackups-does-not-cleanup-jira-3361-tp3994156.html
Sent from the Solr - User mailing list archive at Nabble.com.

thank you James - that is good to know.

for the short-term we'll just use cron and kill backup directories that are
older than x.

for the long-term, we'll just migrate to 4.0

thanks again
--
View this message in context: http://lucene.472066.n3.nabble.com/maxNumberOfBackups-does-not-cleanup-jira-3361-tp3994156p3994191.html
Sent from the Solr - User mailing list archive at Nabble.com.