Return-Path: X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4510961B6 for ; Thu, 26 May 2011 11:23:27 +0000 (UTC) Received: (qmail 12661 invoked by uid 500); 26 May 2011 11:23:26 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 12619 invoked by uid 500); 26 May 2011 11:23:26 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 12611 invoked by uid 99); 26 May 2011 11:23:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 11:23:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of langleyatwork@gmail.com designates 74.125.83.170 as permitted sender) Received: from [74.125.83.170] (HELO mail-pv0-f170.google.com) (74.125.83.170) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 11:23:19 +0000 Received: by pvh21 with SMTP id 21so503408pvh.1 for ; Thu, 26 May 2011 04:22:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=c2BI1/M/Mh1OwvfVd1JBP1WgCE+D5JyPpnwD3KgpKJc=; b=OcfGacwB2r4w9e1Uvec1pMUDdMQ1z375KjrIten4PyOu4rQRftDCLHMwPkbC64eUb5 crP52Dp0O7VJxa6Z9kDSxnpQZRkqENo2XOwZ8v8DaTVocLLRqThoA1TT9GH2KfTJGgl5 uepGFqxvjeqqmsZ2OnZoG/w5y9951XFYQdZZg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Rq+kuEdJgrdbPc8Umuybda3T/c/gjtuJ2E+LR2yriOTpjGtKcdKMo9l38WHgWyMHI1 2L3RQO2mHCYvxXqP1wBihlbWS4lcA2eBIyISoZdD5f3B4pxyCLh6wer8uj4M6Ueu3fLs arBO9FH+RsyUrX2AyQecV5QcLrF9nw1TDJXZY= MIME-Version: 1.0 Received: by 10.142.80.2 with SMTP id d2mr125267wfb.214.1306408979224; Thu, 26 May 2011 04:22:59 -0700 (PDT) Received: by 10.142.191.15 with HTTP; Thu, 26 May 2011 04:22:59 -0700 (PDT) Date: Thu, 26 May 2011 07:22:59 -0400 Message-ID: Subject: clustered garbage collection From: John Langley To: users@jackrabbit.apache.org Content-Type: multipart/alternative; boundary=001636e1fd892358ef04a42c0b56 --001636e1fd892358ef04a42c0b56 Content-Type: text/plain; charset=ISO-8859-1 First off, thanks to writers of this great little description of how to do garbage collection and Fabian for pointing it out. http://wiki.apache.org/jackrabbit/DataStore#Data_Store_Garbage_Collection My next question concerns running garbage collection in a cluster. If had a number of identical nodes running in a cluster, each of them periodically running a garbage collection task, where the periods may overlap... say nodes 1 starts and then in the middle of either the mark or the sweep, node 2 starts it's mark or perhaps even overlaps it's sweep.... what will the consequences be? Will they "collide", i.e. will their be unexpected errors (explicit exception based errors) or mis-behaviors (implicit non-identified errors)? Of course, the alternative is to guarantee that only one node in the cluster is responsible for the periodic mark and sweep. Thanks in advance for any pointers or insights. This community has been GREAT at responding to questions with very helpful solutions and bug fixes. -- Langley --001636e1fd892358ef04a42c0b56--