[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634044#action_12634044
]
Marcel Reutegger commented on JCR-1753:
---------------------------------------
I have the same concerns regarding the visibility of the method.
I'm also wondering if this is really needed. IIUC the cluster works like an
eventually consistent system (see [1] for an introduction). If the application
can guarantee 'session consistency' (i.e. an application session always uses a
given cluster node and only switches to another cluster node when it goes down)
the consequences of the inconsistency window should be very limited.
Micah, can you please elaborate why you need a cluster node to be in sync? Even
if you can sync a cluster node, it might get out of sync again right away by a
modification of another cluster node.
[1] http://www.allthingsdistributed.com/2007/12/eventually_consistent.html
> 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
> Fix For: 1.5
>
> Attachments: 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.
