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
Attachments: patch_commit_2eed44310e71.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
