[
https://issues.apache.org/jira/browse/JCR-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister resolved JCR-3138.
------------------------------------
Resolution: Fixed
Implemented as optional behavior that can be switched on with a subclass
overridable.
> 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
