lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless" <>
Subject Re: restoring a corrupt index?
Date Sat, 10 Nov 2007 21:34:20 GMT

"Yonik Seeley" <> wrote:
> On Nov 10, 2007 4:01 PM, Ryan McKinley <> wrote:
> > Using solr, we have been running an indexing process for a while and
> > when I checked on it today, it spits out an error:
> >
> > java.lang.RuntimeException:
> > /path/to/index/_cf9.fnm (No such file or directory)
> >         at org.apache.solr.core.SolrCore.getSearcher(
> >         at org.apache.solr.core.SolrCore.getSearcher(
> >
> > Looking through the archives, it looks like we are up a creek.
> >
> > Any thoughts on what could have caused this?  The log files contains
> > some 'too many open files' errors, I can't tell if that corresponds with
> > when the index went bad though.
> Yup... that would most likely be it.

How can this lead to index corruption?  The "no such file or directory" on
loading _cf9.fnm sounds like index corruption?

Or maybe the index is not corrupt but then we are hitting the descriptor limit
on opening a searcher and it's being reported as "no such file or directory"?

If so, maybe opening an IndexWriter and optimizing the index would recover
it?  (Make a backup copy of the index first!).

> > 2. Does the ulimit number explain how the index got corrupted?  If so,
> > it seems like a problem.
> I think newest lucene versions would prevent this with
> lucene_autocommit=false.  A new segments file (the file which
> references all other files in the current index) is not written until
> a close of the writer.

Yonik do you understand why so many unreferenced files are being produced
here?  What's the root cause?


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

View raw message