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] Updated: (JCR-1087) Maintain the cluster revision table
Date Fri, 26 Oct 2007 12:27:50 GMT

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

Martijn Hendriks updated JCR-1087:
----------------------------------

    Attachment: JCR-1087.patch

Attached is a patch for this issue. When a DatabaseJournal is used, the local revisions are
also stored in the database instead of on the local file system. This information can then
be used for periodic clean-ups of the JOURNAL table which may become very large. Note that
this only works if all JR information except for the search index is stored in the database.
The clean-up thread is disabled by default.

Please comment. Thanks!

> 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, JCR-1087.patch
>
>
> 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.


Mime
View raw message