From users-return-17468-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Sun May 8 10:29:20 2011 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 836623971 for ; Sun, 8 May 2011 10:29:20 +0000 (UTC) Received: (qmail 53961 invoked by uid 500); 8 May 2011 10:29:19 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 53925 invoked by uid 500); 8 May 2011 10:29:19 -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 53917 invoked by uid 99); 8 May 2011 10:29:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 May 2011 10:29:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael.wechner@wyona.com designates 195.226.6.75 as permitted sender) Received: from [195.226.6.75] (HELO mail.wyona.com) (195.226.6.75) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 May 2011 10:29:10 +0000 Received: from michael-wechners-macbook-pro-3.local (32-100.78-83.cust.bluewin.ch [83.78.100.32]) by mail.wyona.com (Postfix) with ESMTPA id CA5592DA42C for ; Sun, 8 May 2011 12:36:37 +0200 (CEST) Message-ID: <4DC67061.1070205@wyona.com> Date: Sun, 08 May 2011 12:28:49 +0200 From: Michael Wechner User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: users@jackrabbit.apache.org Subject: Re: Add new nodes to a cluster References: <4DA6BC64.5080907@chregu.tv> <4DABFBE1.7020300@wyona.com> <4DAC3A0E.6070302@liip.ch> <4DAD7EF4.9020202@liip.ch> <4DBFAC61.4080001@chregu.tv> In-Reply-To: <4DBFAC61.4080001@chregu.tv> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Thanks very much for this summary. Maybe you can add it to the Wiki http://wiki.apache.org/jackrabbit/Clustering ;-) Thanks Michael On 5/3/11 9:18 AM, Christian Stocker wrote: > Hi > > Just a little update on that, the following procedure seem to work > > - shutdown instance > - get number from JOURNAL_LOCAL_REVISIONS > - cp -r jackrabbit jackrabbit.bkup > - mv jackrabbit.bkup to another server > - change repository with new nodename in clusterconfig > - add that to JOURNAL_LOCAL_REVISIONS with the number from above > - done ;) > > > I'll try to make a little script for that and document it > > THanks for all the input > > christian > > On 19.04.11 14:24, Christian Stocker wrote: >> Hi all >> >> thanks a lot for your answers, looks good to me and we will proceed ;) >> >> christian >> >> On 19.04.11 13:46, Jeroen Reijn wrote: >>>>> >>>>> On 18.04.11 11:04, Jeroen Reijn wrote: >>>>>>> I'm also not 100% sure, but I can second Alex his answer. >>>>>>> > From what I've seen the new cluster node will start from the persisted >>>>> data >>>>>>> and will continue from there on with using the journal. >>>>> The question is then, how does the new cluster node know on which >>>>> position he should start? Or do we "just" have to make sure, that >>>>> nothing writes between the start of the new node and "when it's ready". >>>>> How do we know it's ready then? >>>>> >>> If you're using a database I know that there is a table in which Jackrabbit >>> stores the global revision, which is the latest revision. All the nodes in >>> the cluster will work towards that revision based on the repository journal. >>> My best bet would be that when a new node in the cluster starts, it starts >>> from this global revision. >>> >>> Next to the global_revision table, there is also a local_revision table that >>> contains the current revision for each node in the cluster. >>> >>> >>>