You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Martijn Hendriks (JIRA)" <ji...@apache.org> on 2007/10/17 15:39:50 UTC
[jira] Updated: (JCR-1087) Maintain the cluster revision table
[ https://issues.apache.org/jira/browse/JCR-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn Hendriks updated JCR-1087:
----------------------------------
Attachment: cluster-trace.txt
When the cluster revision table becomes too large a cluster node without search index and local revision number cannot be started due to memory problems (see attached stacktrace).
> 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.