Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9EFC07ED9 for ; Tue, 29 Nov 2011 16:46:01 +0000 (UTC) Received: (qmail 64951 invoked by uid 500); 29 Nov 2011 16:46:01 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 64921 invoked by uid 500); 29 Nov 2011 16:46:01 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 64914 invoked by uid 99); 29 Nov 2011 16:46:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 16:46:01 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2011 16:46:00 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 2B02CA6C24 for ; Tue, 29 Nov 2011 16:45:40 +0000 (UTC) Date: Tue, 29 Nov 2011 16:45:40 +0000 (UTC) From: "Dominique Pfister (Resolved) (JIRA)" To: dev@jackrabbit.apache.org Message-ID: <1888258227.22266.1322585140177.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <968342929.6249.1320661071694.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (JCR-3138) Skip sync delay when changes are found MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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