[
https://issues.apache.org/jira/browse/JCR-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Hendriks resolved JCR-1087.
-----------------------------------
Resolution: Fixed
Committed in revision 628697.
The instance revision on the local file system is automatically migrated to the
database (to the LOCAL_REVISIONS) table. The clean-up thread is not started by
default.
Known caveats of the current solution:
- The user must make sure that all cluster nodes have written their local
revision to the database before the clean-up thread runs for the first time
because otherwise cluster nodes might miss updates (because they have been
purged) and their local caches and search-indexes get out of sync.
- If a cluster node is removed permanently from the cluster, then its entry in
the LOCAL_REVISIONS table should be removed manually. Otherwise, the clean-up
thread will not be effective.
> 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
> Assignee: Martijn Hendriks
> Priority: Minor
> 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.
