Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 48345 invoked from network); 14 Aug 2007 07:06:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Aug 2007 07:06:54 -0000 Received: (qmail 18166 invoked by uid 500); 14 Aug 2007 07:06:51 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 18148 invoked by uid 500); 14 Aug 2007 07:06:51 -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 18139 invoked by uid 99); 14 Aug 2007 07:06:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2007 00:06:51 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.146.181] (HELO wa-out-1112.google.com) (209.85.146.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2007 07:06:48 +0000 Received: by wa-out-1112.google.com with SMTP id m34so2445806wag for ; Tue, 14 Aug 2007 00:06:28 -0700 (PDT) Received: by 10.114.60.19 with SMTP id i19mr2317199waa.1187075187464; Tue, 14 Aug 2007 00:06:27 -0700 (PDT) Received: by 10.114.190.4 with HTTP; Tue, 14 Aug 2007 00:06:27 -0700 (PDT) Message-ID: Date: Tue, 14 Aug 2007 09:06:27 +0200 From: "Dominique Pfister" Sender: dpfister@day.com To: users@jackrabbit.apache.org Subject: Re: jackrabbit clustering In-Reply-To: <20070813153251.250840@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20070813153251.250840@gmx.net> X-Google-Sender-Auth: f096d9087a9627fc X-Virus-Checked: Checked by ClamAV on apache.org Hi Philipp, On 13/08/07, astrograph@gmx.net wrote: > hi, > > we have a repository which contains a lot of big binary data, we want to = use clustering, and have the following questions: > > - Is there a way to configure the db connection used for the journal in a= different way than to give the jdbc connection parameters? A jndi data sou= rce would be more useful to us. Not yet. If you'd like to see this feature, please file a JIRA issue. > - With the clustered configuration we are limited to a db persistence man= ager, with the kind of data we ingest into our system we see a huge increas= e in the time it takes to process them. I think this is caused by the db pe= rsistence manager - do we REALLY have to use a db persistence manager? I'm afraid so, yes. File-based persistence managers do not provide transaction isolation, e.g. one cluster node could potentially overwrite elements in the file system before the whole operation is actually committed. > - we found that you don=B4t need to give a cluster id, it seems there is = an algorithm to provide individual servers with cluster ids - is this safe = to use? This algorithm assigns a random cluster id to a cluster node: I'd rather use a well-defined, sensible cluster id, which also helps when tracking down what cluster node was responsible for a change. > - versioning is still configured for the local file system, is this ok fo= r a clustered installation? No, again you'll need a db persistence manager. Kind regards Dominique