You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Berteau (JIRA)" <ji...@apache.org> on 2006/04/18 23:01:17 UTC
[jira] Created: (LUCENENET-4) Index Optimization
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
[jira] Commented: (LUCENENET-4) Index Optimization
Posted by "eyal post (JIRA)" <ji...@apache.org>.
[ 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