Thanks for this Dominique. RE "..after having verified that every node in the cluster has read all outstanding changes.."
To be clear, I need to check the value in the revision.log to the latest number in the journal? Regards, Shaun -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dominique Pfister Sent: 17 December 2007 10:38 To: [email protected] Subject: Re: JackRabbit Journal table growing very large - archive strategy? Hi Shaun, old journal entries may be removed as follows: after having verified that every node in the cluster has read all outstanding changes, you may delete all entries in the revision table JOURNAL (when using the DatabaseJournal) or delete all journal.log files in the journal directory (when using the FileJournal). Kind regards Dominique On 16/12/2007, sbarriba <[EMAIL PROTECTED]> wrote: > Hi Dominique et al, > > We've been running a 2 node clustered JackRabbit for a few months. > > The journal table has grown to 1.1GB. > > > > Any guidance on how the admin procedure to delete old data from this table? > > Regards, > > Shaun > > > > > > > > > >
