Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 4009 invoked from network); 4 Feb 2011 09:19:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Feb 2011 09:19:55 -0000 Received: (qmail 53229 invoked by uid 500); 4 Feb 2011 09:19:54 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 52844 invoked by uid 500); 4 Feb 2011 09:19:51 -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 52831 invoked by uid 500); 4 Feb 2011 09:19:50 -0000 Delivered-To: apmail-incubator-jackrabbit-dev@incubator.apache.org Received: (qmail 52828 invoked by uid 99); 4 Feb 2011 09:19:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Feb 2011 09:19:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of stefan.guggisberg@gmail.com designates 209.85.213.175 as permitted sender) Received: from [209.85.213.175] (HELO mail-yx0-f175.google.com) (209.85.213.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Feb 2011 09:19:43 +0000 Received: by yxd5 with SMTP id 5so864584yxd.6 for ; Fri, 04 Feb 2011 01:19:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=+JkeBxTZOvr1OivUpTs8nXe4e4zZgaXImPD3dt2NwrU=; b=sJB8i5uC01oc7+US3iTZwU9BH6Cl1JKGFpDbFd1O5wjjGAifx4OGkzoVZvB9hLMDE+ aAtfhDUgA7XAEdwmSfsft69k2N6AYCLQv6u/mXdMubyeNl1cnFgwIsbrykuSPKdRf0CI K2/aCHCjtaTxA84hc1o72PwfUDp/aC+m8IxdA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=iYu6BbwtdeHUC6BLuxp2vCVaX2aT+V+LgQUu/9YcSfN+nogasn1n28r94yLTOuPFWH r+PTk+yMSos5jyomI6N8moafFhQgR69V6bt4bkEnH6wo1wkWkcwVQrMrNjWiC+Jme5bK Yes3L/aztxc+2iJMmvyisLnz3Y4jdRKO+RdqA= MIME-Version: 1.0 Received: by 10.100.105.6 with SMTP id d6mr7269222anc.89.1296811162637; Fri, 04 Feb 2011 01:19:22 -0800 (PST) Received: by 10.100.144.2 with HTTP; Fri, 4 Feb 2011 01:19:22 -0800 (PST) In-Reply-To: References: <14c355f2286a533132b75b1a57f7f891@obinary.com> <42AE9C3F.3080302@gmx.net> Date: Fri, 4 Feb 2011 10:19:22 +0100 Message-ID: Subject: Re: indexing, jackrabbit & cqfs From: Stefan Guggisberg To: jackrabbit-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jun 14, 2005 at 3:19 PM, Boris Kraft wrot= e: > On 14.06.2005, at 10:58, Marcel Reutegger wrote: > >> Boris Kraft wrote: >>> >>> Is it still possible to turn of indexing (and versioning while I am at >>> =A0it) with the current release of jackrabbit? >> >> If you comment out the SearchIndex tag in the workspace.xml you can >> disable the QueryManager / Indexing. > > Thanks > >>> The reason why I am asking is that with my latest build (from last >>> =A0Saturday) I have serious problems to get a stable repository using = =A0cqfs. >>> In particular, the repository breaks and the indexer writes out =A0inde= x.dat >>> files with a size of ~100GB (yes, thats Gigabyte). Obviously, =A0I am n= ot >>> really happy about that. >>> Does anybody else experience similar behavior? >> >> Nope, haven't seen this before. >> It seems that you are using CQFS as the underlying filesystem for the >> search index. If this is true, I recommend to use LocalFileSystem. >> >> One reason for the huge index.dat file might be that the configuration f= or >> CQFS is not apropriate for the use as a filesystem for search index. e.g= . >> the blocksize parameter has an influence on the maxmimum file size that = can >> be created in CQFS. > > Yes, that might be a good idea. > > I am currently moving from cqfs to filesystem and up to now this looks qu= ite > promising (except for the number of files I now have). The repository is = now > stable again. It might be an issue with CQFS on OSX, I'll let you know if wrong list. since cqfs is a commercial product, please contact your product support cha= nnel. cheers stefan > problems go away when run on windows. > > Thanks again > - Boris > >