Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <24197951.1194508251096.JavaMail.jira@brutus>
Date: Wed, 7 Nov 2007 23:50:51 -0800 (PST)
From: "Martijn Hendriks (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-1087) Maintain the cluster revision table
In-Reply-To: <30977810.1187952210738.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Martijn Hendriks commented on JCR-1087:
---------------------------------------

Hi Dominique,

Good point! When this patch is applied to a Jackrabbit installation that already uses the clustering feature it will break if the LOCAL_REVISIONS table is not added manually. I'll look into this.

Martijn

> 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.