You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by sbarriba <sb...@yahoo.co.uk> on 2007/12/16 20:24:22 UTC
JackRabbit Journal table growing very large - archive strategy?
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
RE: JackRabbit Journal table growing very large - archive strategy?
Posted by sbarriba <sb...@yahoo.co.uk>.
For those using clustering with a database backed journal, its worth noting
that you should include a scheduled task to periodically delete old records
from the journal table (this table gets large over time).
Probably also with including something to this effect in the associated
docs.
Regards,
Shaun
-----Original Message-----
From: sbarriba [mailto:sbarriba@yahoo.co.uk]
Sent: 17 December 2007 22:13
To: users@jackrabbit.apache.org
Subject: RE: JackRabbit Journal table growing very large - archive strategy?
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: dpfister@day.com [mailto:dpfister@day.com] On Behalf Of Dominique
Pfister
Sent: 17 December 2007 10:38
To: users@jackrabbit.apache.org
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 <sb...@yahoo.co.uk> 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
>
>
>
>
>
>
>
>
>
>
RE: JackRabbit Journal table growing very large - archive strategy?
Posted by sbarriba <sb...@yahoo.co.uk>.
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: dpfister@day.com [mailto:dpfister@day.com] On Behalf Of Dominique
Pfister
Sent: 17 December 2007 10:38
To: users@jackrabbit.apache.org
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 <sb...@yahoo.co.uk> 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
>
>
>
>
>
>
>
>
>
>
RE: JackRabbit Journal table growing very large - archive strategy?
Posted by dainius rygelis <da...@pitchpointsolutions.com>.
Is there a howto available that describes the steps needed to verify?
Regards,
Dainius
-----Original Message-----
From: dominique.pfister@day.com [mailto:dominique.pfister@day.com]
Sent: December-17-07 5:38 AM
To: users@jackrabbit.apache.org
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 <sb...@yahoo.co.uk> 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
>
>
>
>
>
>
>
>
>
>
Re: JackRabbit Journal table growing very large - archive strategy?
Posted by Dominique Pfister <do...@day.com>.
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 <sb...@yahoo.co.uk> 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
>
>
>
>
>
>
>
>
>
>