jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bart van der Schans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2968) Add an option to read the Clustering Journal from a different source than the rest of the clustering info
Date Thu, 06 Oct 2011 16:37:29 GMT

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

Bart van der Schans commented on JCR-2968:

Hi Christian, Jukka,

I've been working on the same/similar use case (running jackrabbit on a database slave) a
little while ago. However we have the extra requirement that there are no connections going
back from the "slave" environment to the master. For example when the master is locate inside
the office which replicates to one or more (multi geo) locations on the internet. The use
case is slightly different so both solutions can coexists. If that's what we want I can create
a separate issue.

The solution I chose is to store the locale revisions on the file system. This way you don't
need to setup an extra database connection for the "read-only" locale revisions datasource.
I've attached the patch (against 2.2). You can also view the diff at:


The idea of the patch is that instead of a DatabaseJournal you would configure a DatabaseSlaveJournal
and point the datasource to the slave database in the repository.xml. The configuration stays
identical to the regular DatabaseJournal.



> Add an option to read the Clustering Journal from a different source than the rest of
the clustering info
> ---------------------------------------------------------------------------------------------------------
>                 Key: JCR-2968
>                 URL: https://issues.apache.org/jira/browse/JCR-2968
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: clustering, jackrabbit-core
>            Reporter: Christian Stocker
>            Assignee: Jukka Zitting
>             Fix For: 2.3.1
>         Attachments: 0001-JCR-2968-Add-an-option-to-read-the-Clustering-Journa.patch,
> This patch adds the possibility to read (but not write) the Cluster JOURNAL from a different
source than the rest of the cluster information. This makes it possible to setup a master/slave
DB setup, where everything cluster related is read from the slave, but writes to the master.
It reads the actual data also from the slave and assumes that this jackrabbit instance never
does any writes (except for updating the cluster index position in the DB). We have to read
the Cluster Journal from the slave to guarantee a consistent state
> More info why and how is here
> http://blog.liip.ch/archive/2011/05/04/how-to-make-jackrabbit-globally-distributable-fail-safe-and-scalable-in-one-go.html
> I didn't write any tests yet, if you can point me, where I should add them, I'll gladly
do them.
> Would be great, if we could integrate that in any of the future Jackrabbit releases.
> It's of course fully backwards compatible, nothing changes, if you don't sepcify 
>  <param name="dataSourceNameJournalRead">
> in repository.xml

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message