lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Ritchie <>
Subject Compound file index issue
Date Wed, 14 Jan 2004 15:46:57 GMT
We've started using the new compound indexing functionality available in lucene 1.3 final however

we've been seeing an issue that I haven't quite resolved and was hoping that people on this
might be able to lend help on.

The stack trace of the issue is:

2004.01.13 18:15 [] /var/search/BfUfO9s1/_qb5.fnm (No such file or directory)
         at Method)
         at org.apache.lucene.index.FieldInfos.<init>(
         at org.apache.lucene.index.SegmentReader.<init>(
         at org.apache.lucene.index.SegmentReader.<init>(
         at org.apache.lucene.index.IndexReader$1.doBody(

The error seems obvious enough from a quick glance of the above code - the file was been deleted.

However, since we are using compound indexing there should be a /var/search/BfUfO9s1/_qb5.cfs
however that file does not exist. The only files in the search directory are:

-bash-2.05b$ ls -l
total 6908
-rw-r--r--    1 resin    js              4 Jan 13 18:14 deletable
-rw-r--r--    1 resin    js        7029055 Jan 13 10:03 _qau.cfs
-rw-r--r--    1 resin    js              9 Jan 13 18:14 _qb5.del
-rw-r--r--    1 resin    js          16060 Jan 13 18:14 _qb7.cfs
-rw-r--r--    1 resin    js             34 Jan 13 18:14 segments

 From what I can tell it seems to me that the segments are somehow getting out of sync with
what is 
actually on the filesystem somehow.

Any suggestions are where to start looking for the cause of this bug?


Bruce Ritchie

View raw message