jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1087) Maintain the cluster revision table
Date Sun, 21 Oct 2007 13:06:50 GMT

    [ https://issues.apache.org/jira/browse/JCR-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536504

Martijn Hendriks commented on JCR-1087:

The resolution of JCR-905 allows us to remove all unnecessary revision data. I.e., the minimum
of all local revisions of the clusternodes gives an upperbound on the revisions that can safely
be removed from the database.

A solution for this issue would be to add a periodic task that removes all unnecessary revisions:
- All clusternodes should add their local revision to the database.
- Add a configuration option in the repository.xml to let one of the clusternodes execute
the cleanup task (i.e., period and offset such as "every night at 00:00 hours").

> Maintain the cluster revision table
> -----------------------------------
>                 Key: JCR-1087
>                 URL: https://issues.apache.org/jira/browse/JCR-1087
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering
>    Affects Versions: 1.3
>         Environment: A clustered Jackrabbit
>            Reporter: Martijn Hendriks
>            Priority: Minor
>         Attachments: cluster-trace.txt
> The revision table in which cluster nodes write their changes can potentially become
very large. If all cluster nodes are up to date to a certain revision number, then it seems
unnecessary to keep the revisions with a lower number.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message