You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christian Schröder (JIRA)" <ji...@apache.org> on 2009/01/06 20:54:44 UTC

[jira] Commented: (JCR-1087) Maintain the cluster revision table

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

Christian Schröder commented on JCR-1087:
-----------------------------------------

prepare Statements already uses the LOCAL_REVISIONS table. Because of this the checkLocalRevisionSchema() will be too late and startup fails.

checkLocalRevisionSchema() should be called in checkScheme();

> Maintain the cluster revision table
> -----------------------------------
>
>                 Key: JCR-1087
>                 URL: https://issues.apache.org/jira/browse/JCR-1087
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: clustering, jackrabbit-core
>         Environment: A clustered Jackrabbit
>            Reporter: Martijn Hendriks
>            Assignee: Martijn Hendriks
>            Priority: Minor
>             Fix For: 1.5.0
>
>         Attachments: cluster-trace.txt, JCR-1087-v2.patch, 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.