jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1753) Allow means force a Repository to synchronize with the cluster
Date Wed, 24 Sep 2008 13:42:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634140#action_12634140

Micah Whitacre commented on JCR-1753:

My use case is described in the mailing list link included in the first comment.  I read the
article you linked to and it was very interesting.  In my situation we are shooting for session
consistency however there is not means to guarantee the stickiness of the session on the server
side.  The setup I have is operations are routed between 3 different JVMs and each JVM is
read/writing to the JCR repository.  So the use case I'm shooting for is client 1 performs
writes which get routed to JVM1.  The same client then performs a read on that write however
the operation is routed to JVM2.  In this situation I know that the write operation has occurred
but when retrieving from the repository get a PathNotFoundException.  So in that case I'd
like to sync to update JVM2.  After I sync I attempt to read and either get the value I'm
looking for or I don't.  If i don't then I know that a concurrent modification has occurred
and report the appropriate response back to the client.  

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

View raw message