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-3138) Skip sync delay when changes are found
Date Mon, 07 Nov 2011 10:45:51 GMT

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

Bart van der Schans commented on JCR-3138:
------------------------------------------

Hi Dominique,

The "master" (although in a JR cluster all nodes are equal) writes it's changes to the database
in a clustered setup. The slave queries the database (and not the JR node) for changes. So
even when all other nodes are down the slave will just pull the changes from the database.
As long as the database is running there is no riks of loosing data or endangering the integrity.


BTW, if you want to pull in changes on the slave you can do  a Session.refresh(). This will
force the ClusterNode to perform a sync().

Regards,
Bart
                
> 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

        

Mime
View raw message