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 6F6C110E71 for ; Thu, 10 Apr 2014 14:02:46 +0000 (UTC) Received: (qmail 32754 invoked by uid 500); 10 Apr 2014 14:02:45 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 32658 invoked by uid 500); 10 Apr 2014 14:02:39 -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 32644 invoked by uid 99); 10 Apr 2014 14:02:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Apr 2014 14:02:37 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.246.2.115] (HELO prod-mail-xrelay07.akamai.com) (72.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Apr 2014 14:02:31 +0000 Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id DDFFE4743B for ; Thu, 10 Apr 2014 14:02:07 +0000 (GMT) Received: from prod-mail-relay06.akamai.com (prod-mail-relay06.akamai.com [172.17.120.126]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id CD11347431 for ; Thu, 10 Apr 2014 14:02:07 +0000 (GMT) Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub4.kendall.corp.akamai.com [172.27.105.20]) by prod-mail-relay06.akamai.com (Postfix) with ESMTP id C09A82029 for ; Thu, 10 Apr 2014 14:02:07 +0000 (GMT) Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by USMA1EX-CASHUB4.kendall.corp.akamai.com ([172.27.105.20]) with mapi; Thu, 10 Apr 2014 10:02:06 -0400 From: "Dube, Shreyas" To: "users@jackrabbit.apache.org" Date: Thu, 10 Apr 2014 10:02:04 -0400 Subject: Persisting SearchIndex to database Thread-Topic: Persisting SearchIndex to database Thread-Index: Ac9UxXR4JNsjcf/QQGCeljOAgF04Hw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CF6C1C9C7B85sdubeakamaicom_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_CF6C1C9C7B85sdubeakamaicom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello, Background: I=92m evaluating JCR/Jackrabbit as a layer of abstraction for p= ersistence over Oracle. We are using Tomcat6 as the application server. We = usually have 4 =96 8 Tomcat=92s clustered up in the production environment.= I have configured all and stanzas to poi= nt to Oracle (well, I=92m using MySQL now, but that=92ll change). I have NO= T set up clustering in Jackrabbit yet and that is something I want to look = at once I figure out. This is my configuration = for a This configuration ends up creating a bunch of files under ${= wsp.home}/index under the repository home and the workspace home directory. Questions: 1. What are these files storing? I=92m assuming it is the search index. 2. Given that we have a clustered Tomcat setup, would it be possible to p= ersist the search index to the database? 3. If 2 is not possible, are there other search providers that would work= in a clustered environment? 4. Would turning on Jackrabbit clustering sync search indexes across all = nodes? When are search indexes updated in a clustered environment? Thanks, Shreyas --_000_CF6C1C9C7B85sdubeakamaicom_--