[
https://issues.apache.org/jira/browse/JCR-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145556#comment-13145556
]
Dominique Pfister commented on JCR-3138:
----------------------------------------
Hi Bart,
not quite: we already have our own journal implementation, derived from
o.a.j.core.journal.AbstractJournal, and what I'd like to do now is break the
body of doSync() into multiple steps that can be separately invoked by a
subclass without having to resort to copy-paste. AFAICS, JCR-2968 is related to
database journaling, whereas our implementation is not, so I don't think these
two issues should be combined, what do you think?
Dominique
> Skip sync delay when changes are found
> --------------------------------------
>
> Key: JCR-3138
> URL: https://issues.apache.org/jira/browse/JCR-3138
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: clustering
> Affects Versions: 2.3.2
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
> The cluster synchronization on a slave does always wait for some time (as
> specified in the sync delay) before fetching changes. If a lot of changes are
> being written to the master, a slave will considerably fall behind the master
> in term of revisions, which may endanger the integrity of the cluster if the
> master will crash. I therefore suggest that a slave should rather immediately
> contact the master again after some changes have been found, until it sees no
> more changes.
--
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
