Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 81527 invoked from network); 21 Apr 2006 06:46:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 06:46:13 -0000 Received: (qmail 55917 invoked by uid 500); 21 Apr 2006 06:46:10 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 55885 invoked by uid 500); 21 Apr 2006 06:46:10 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 55872 invoked by uid 99); 21 Apr 2006 06:46:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 23:46:10 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 23:46:09 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 89E367142E2 for ; Fri, 21 Apr 2006 06:45:06 +0000 (GMT) Message-ID: <22359541.1145601906547.JavaMail.jira@brutus> Date: Fri, 21 Apr 2006 06:45:06 +0000 (GMT+00:00) From: "eyal post (JIRA)" To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENENET-4) Index Optimization In-Reply-To: <11856765.1145394077618.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/LUCENENET-4?page=comments#action_12375496 ] eyal post commented on LUCENENET-4: ----------------------------------- Jira (The issue tracker) is not the place to ask questions about Lucene. Please use the mailing lists for that: http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-user/ After this is discussed in the mailing list and it is confirmed to be a bug, Then a it should be reported in Jira. > Index Optimization > ------------------ > > Key: LUCENENET-4 > URL: http://issues.apache.org/jira/browse/LUCENENET-4 > Project: Lucene.NET > Type: Bug > Environment: Windows server 2003 > Reporter: Steve Berteau > > We are using Lucene .NET Beta 1.9 version 1. > We have been indexing about 300 000 documents with a compound index of 630 Mb and using frequently the optimize function to compress without problem. > As we kept indexing more documents (300,000 +) into this file, we are getting a corrupted index and the optimization stop (file stop growing up at about 480 Mb) and never complete the optimization correctly. > Does anybody have seen this problem ? > Is there a way to avoid index corruption ? > What could be the corruption source ? > Does the corrupted index could be repaired ? > Should we create multiple index ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org