Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 76717 invoked from network); 25 Mar 2008 01:50:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Mar 2008 01:50:00 -0000 Received: (qmail 8980 invoked by uid 500); 25 Mar 2008 01:49:53 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 8718 invoked by uid 500); 25 Mar 2008 01:49:52 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 8707 invoked by uid 99); 25 Mar 2008 01:49:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 18:49:52 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates 209.85.162.182 as permitted sender) Received: from [209.85.162.182] (HELO el-out-1112.google.com) (209.85.162.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2008 01:49:13 +0000 Received: by el-out-1112.google.com with SMTP id y26so1447245ele.4 for ; Mon, 24 Mar 2008 18:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=1OsXE809uNYSI2R3VGJDOTMyR7ye0gQWcq5FKm3vH2Y=; b=uXMTLjG0QIBeUNCGCeYTc47bZGtdgsv98yHaXblyFN6sEUE8oxUZVoOtUWogpGyMGBo1Hbn9cRgoEy7x8THe3jk/F5VcqFsbb93Ks93MVFUqYUtWT5tpSV3LVkBLtZ0nlJGLz802GO4Mkq1Qd6t8DYGOHYRGOSJnYg6BrFiz4sc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=B6QA00OC1G/D4MqKzFZpB7nK7NfPpodHBcKOaYJQIC3z0eVmaj5OBasyPPVq9dAttB/ufFXT+NxUqP3/mMzkbsdESIM3UCU0ZvzLLkePwnjaysHygXHrTxBPF7yGys3lSWny+BCc20q7ictaT4U4aPtv1VfRZv++Tepnu8fhrzQ= Received: by 10.150.195.21 with SMTP id s21mr3642658ybf.9.1206409764447; Mon, 24 Mar 2008 18:49:24 -0700 (PDT) Received: by 10.150.156.2 with HTTP; Mon, 24 Mar 2008 18:49:24 -0700 (PDT) Message-ID: Date: Mon, 24 Mar 2008 21:49:24 -0400 From: "Yonik Seeley" Sender: yseeley@gmail.com To: general@lucene.apache.org Subject: Re: how to control the disk size of the indices Cc: java-user@lucene.apache.org In-Reply-To: <331829.59350.qm@web50304.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <331829.59350.qm@web50304.mail.re2.yahoo.com> X-Google-Sender-Auth: d9528d18cebfa44e X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Mar 24, 2008 at 9:34 PM, Otis Gospodnetic wrote: > Hi Yannis, > > I don't think there is anything of that sort in Lucene, but this shouldn't be hard to do with a process outside Lucene. Of course. optimizing an index increases its size temporarily, so your external process would have to take that into account and play it safe. You could also set mergeFactor to 1, which should keep your index in a fully optimized state MergeFactor must be >= 2 You will always need to allow for double the index size due to increased temporary disk usage during segment merges (including optimize). Peak use on a system being searched and indexed concurrently will often be even higher since currently open readers reference files that have been deleted. -Yonik --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org