On Tue, May 10, 2011 at 6:57 AM, Ashok <[email protected]> wrote: > Hi, > > We are using JackRabbit 2.0. > > We are currently testing Jackrabbit in clustering setup. We have 2 servers > with Jackrabbit installed and we are storing all the datas in 1 database. > > We observed that {Clustering_prefix}_journal and {Workspace_prefix}_bundle > table are growing very significantly. Is there any documented way for > purging these tables? We saw some responses for purging of > {Clustering_prefix}_journal tables stating > > "old journal entries may be removed as follows: after having verified that > every node in the cluster has read all outstanding changes" > > How can we verify that every node in the cluster has read all outstanding > changes programatically? We went through > "DatabaseJournal.RevisionTableJanitor" cleanUpOldRevisions(). Can we use > this?
Yes you can use that. Do keep in mind you do this on 1 of the X nodes. See http://wiki.apache.org/jackrabbit/Clustering for more information > If so, how can we purge {Workspace_prefix}_bundle table? > As far as I know you can't purge this table, because it contains vital data, but I'm not an expert so I might be wrong. > > Any pointers will be of great help. > > -- > Cheers, > Ashok > +91-9600117508 >
