lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eyal post (JIRA)" <>
Subject [jira] Commented: (LUCENENET-4) Index Optimization
Date Fri, 21 Apr 2006 06:45:06 GMT
    [ ] 

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:

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:
>      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:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message