Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 59467 invoked from network); 9 Nov 2006 18:14:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Nov 2006 18:14:59 -0000 Received: (qmail 72214 invoked by uid 500); 9 Nov 2006 18:15:09 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 72191 invoked by uid 500); 9 Nov 2006 18:15:09 -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 72182 invoked by uid 99); 9 Nov 2006 18:15:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2006 10:15:09 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of dominique.pfister@gmail.com designates 64.233.162.192 as permitted sender) Received: from [64.233.162.192] (HELO nz-out-0102.google.com) (64.233.162.192) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2006 10:14:55 -0800 Received: by nz-out-0102.google.com with SMTP id s18so227451nze for ; Thu, 09 Nov 2006 10:14:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Fpuo++eci8NkxA+3KOYn5eKZ2fjqiBQsELXMCuyGWdbVldfZlnU3bHIe7zVGN+UGG6a1ZhTOC9cYM5h94d1d38Pj1covx97SMxFAw4Gzvp3cztjvSovcnFDNdJazk1RUu0DlAxSuS+v2y29qfB8UuzisMj5ZAycjr+c7dXgbBrg= Received: by 10.35.32.3 with SMTP id k3mr1458853pyj.1163096073680; Thu, 09 Nov 2006 10:14:33 -0800 (PST) Received: by 10.35.16.14 with HTTP; Thu, 9 Nov 2006 10:14:33 -0800 (PST) Message-ID: <66c10f230611091014i700fcae4x404159e32500f755@mail.gmail.com> Date: Thu, 9 Nov 2006 19:14:33 +0100 From: "Dominique Pfister" Sender: dominique.pfister@gmail.com To: dev@jackrabbit.apache.org Subject: Re: [jira] Commented: (JCR-623) Clustering In-Reply-To: <10833607.1163090858323.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7695671.1162826557259.JavaMail.jira@brutus> <10833607.1163090858323.JavaMail.jira@brutus> X-Google-Sender-Auth: 38573872784ac8f7 X-Virus-Checked: Checked by ClamAV on apache.org On 11/9/06, Pankaj Gupta (JIRA) wrote: > [ http://issues.apache.org/jira/browse/JCR-623?page=comments#action_12448517 ] > > Pankaj Gupta commented on JCR-623: > ---------------------------------- > > Thanks for geting started on this issue. Its a high priority one for us and perhaps many other Jackrabbit users. > > Couple of questions: > 1) Is the search index in other clusters also synced up if each cluster has the index in its local disk? Or is it required to have the search index in a common file system? No, the index is synced up automatically, as a result of the events - passed inside the journal record - being delivered. In other words, the search manager, responsible for updating the index, doesn't see a difference between updates made by its own node and changes made by a foreign node. > 2) Are the other clusters updated immediately? For example, if one cluster adds a new node, is it immediately visible to other sessions in other clusters, as is mandated by the JCR spec? Not actively. Other nodes in the cluster see the change inside a given delay (5 seconds is the default) unless they itself try to perform some changes, which causes an immediate sync. Kind regards Dominique