Problem with too much documents and 0.4 version #12

manolopm opened this Issue Aug 3, 2009 · 3 comments


None yet

2 participants


Just upgraded to 0.4 I launch couchdb and I get this from the indexer.
With other databases that are smaller I get no problem.
I've tried to delete the index and try it again, check perms of the files and all that stuff and the problem still there.

[info] [<0.59.0>] - - 'GET' /fisica-nist3/_all_docs_by_seq?startkey=53250&limit=250&include_docs=true 200

[couchdb-lucene] WARN Exception while updating index. /usr/local/bin/lucene/_b.fnm (No such file or directory)

at Method)






at org.apache.lucene.index.FieldInfos.(

at org.apache.lucene.index.SegmentReader.initialize(

at org.apache.lucene.index.SegmentReader.get(

at org.apache.lucene.index.SegmentReader.get(

at org.apache.lucene.index.DocumentsWriter.applyDeletes(

at org.apache.lucene.index.IndexWriter.applyDeletes(

at org.apache.lucene.index.IndexWriter.doFlush(

at org.apache.lucene.index.IndexWriter.flush(

at org.apache.lucene.index.IndexWriter.closeInternal(

at org.apache.lucene.index.IndexWriter.rollbackInternal(

at org.apache.lucene.index.IndexWriter.rollback(

at com.github.rnewson.couchdb.lucene.Index$Indexer.updateIndex(

at com.github.rnewson.couchdb.lucene.Index$


[couchdb-lucene] INFO indexer stopped.

[info] [<0.59.0>] - - 'GET' /fisica-nist3/_all_docs_by_seq?startkey=53500&limit=250&include_docs=true 200


It sounds like you've deleted only part of the index, or you deleted it while couchdb-lucene is running.

Please stop couchdb, delete the whole 'lucene' directory, and start up again. You appear to have corrupted the index by manually deleting some files from it, you need to let couchdb-lucene rebuild from scratch.


Ok, it's seem that something strange happened before. I'll try to delete everything and lauch it again and now works as it should.


Great. Please reopen if the problem occurs without manual deletions.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment