jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3138) Skip sync delay when changes are found
Date Mon, 07 Nov 2011 10:55:51 GMT

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

Dominique Pfister commented on JCR-3138:

Hi Bart,

Thank you for your comment. You're absolutely right, in a standard cluster where the data
itself is in shared storage such as a database, the slave will of course not talk to the master
itself and the data does not get lost when the master crashes. We have a customized setup,
however, where the data is not shared (every cluster node has a complete copy of the data)
and where the slaves actually talk to the master: in order to support such a configuration,
I'd like to make the sync loop more "customizable" by the actual journal implementation.

Kind regards
> 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


View raw message