[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1753:
-------------------------------
Attachment: JCR-1753-sync-in-refresh.patch
Attached the alternative patch (JCR-1753-sync-in-refresh.patch).
With this method the client needs to call session.refresh(...) to force a
cluster sync.
I've also included a static (and public) flag variable,
SessionImpl.clusterSyncOnRefresh, that an application can set to false if it
wants to disable this feature (some applications may have come to expect
refresh to be a nearly instantaneous operation, which no longer is true with
this feature).
> Allow means force a Repository to synchronize with the cluster
> --------------------------------------------------------------
>
> Key: JCR-1753
> URL: https://issues.apache.org/jira/browse/JCR-1753
> Project: Jackrabbit
> Issue Type: New Feature
> Components: clustering, jackrabbit-api, jackrabbit-core
> Reporter: Micah Whitacre
> Assignee: Jukka Zitting
> Attachments:
> 0001-JCR-1753-Allow-means-force-a-Repository-to-synchron.patch,
> 0002-JCR-1753-Allow-means-force-a-Repository-to-synchron.patch,
> JCR-1753-sync-in-refresh.patch, JCR-1753.tar.gz
>
>
> Based on the thread on the user mailing list I'm logging this to propose
> adding a sync() method to force cluster synchronization using the
> JackrabbitRepository extension API.
> The purpose of the method is such that in a distributed clustered environment
> sometime cluster synchronization does or has not occurred such that certain
> repositories are in a stale state. This method would provide a means to
> force a repository to update pull in possible changes made by other
> Jackrabbit repositories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
