Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 18732 invoked from network); 15 Jun 2007 17:04:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jun 2007 17:04:23 -0000 Received: (qmail 77201 invoked by uid 500); 15 Jun 2007 17:04:26 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 76873 invoked by uid 500); 15 Jun 2007 17:04:25 -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 76862 invoked by uid 99); 15 Jun 2007 17:04:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2007 10:04:25 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [85.92.66.10] (HELO cook.mywebserver.net) (85.92.66.10) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2007 10:04:20 -0700 Received: from [86.1.43.209] (helo=tfd.co.uk) by cook.mywebserver.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1HzFDO-0006QK-6a for dev@jackrabbit.apache.org; Fri, 15 Jun 2007 18:04:02 +0100 Received: from shroud.home.tfd.co.uk ([192.168.115.54]) by tfd.co.uk with esmtpa (Exim 4.63) (envelope-from ) id 1HzFDB-0007sj-NF for dev@jackrabbit.apache.org; Fri, 15 Jun 2007 18:03:55 +0100 Message-ID: <4672C675.8090402@tfd.co.uk> Date: Fri, 15 Jun 2007 18:03:49 +0100 From: Ian Boston User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509) MIME-Version: 1.0 To: dev@jackrabbit.apache.org Subject: Journal Maintanence Question Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TFD-Spam-Score: -4.4 (----) X-TFD-Scan-Signature: fcad4b018a4704be8c0267724fbc057f X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cook.mywebserver.net X-AntiAbuse: Original Domain - jackrabbit.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - tfd.co.uk X-Virus-Checked: Checked by ClamAV on apache.org Hi, Quick question, In a FileJournal for a cluster the files get rotated and can be managed, however in a DB journal is their the same rotation or cleanup going on... I think thats right ? In the DatabaseJournal however... I am concerned about having millions of journal records hitting db performance and I was wondering if it would make more sense to have a policy, either records older than the oldest cluster node will be removed or records older than 30 minutes will be removed. Obviously, this will require a snapshot of the local space to seed a new cluster node, and that will have to be fresher than the oldest journal entry. Am I worrying unnecessarily ? Ian