Grokbase Groups Lucene dev July 2008
If your "automatic recycle" means a restart/reboot, the /tmp
directory is probably being cleared by the OS and you might have a
startup race condition.
On Jul 7, 2008, at 2:17 AM, Yajun Liu (JIRA) wrote:

FileNotFoundException in

Key: LUCENE-1328
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affects Versions: 2.1
Environment: OS: Linux version 2.6.9-67.0.1.ELsmp
( (gcc version 3.4.6
20060404 (Red Hat 3.4.6-9)) #1 SMP Fri Nov 30 11:57:43 EST 2007

We use solr 1.2 and the lucene is 2.1.( I don't think this problem
has anything to do with solr.)
Reporter: Yajun Liu

I had this problem for a while. here is how I used lucene index:

1) I don't use compound file.

2) I have a single process and a single thread to update index as
index updater. The index is really small, the mergefactor is 10.
After index is updated, the same thread copies the index to a tmp
directory, validate the index in the tmp directory by:

IndexReader reader =;

then rename the tmp directory to a snapshot_timestamp;

3) the snapshot_timestamp is rsyn to search nodes which DO NOT
update index.

4) We automatically stop and start index updater and search nodes
every midnight. (don't ask me why)

Here is what I observed:

1) Not always, sometimes when index updater is started during our
automatic recycle, we got /var/tmp/index/_gw.fnm (No such file
or directory)
at Method)
at org.apache.lucene.index.FieldInfos.<init>
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.IndexReader$1.doBody
at org.apache.lucene.index.SegmentInfos$

Note each time, the missing file is different. When this happen,
the program automatically tried to reopen the most recent THREE
snapshots and we got the same exception for each snapshot.
Remember, each of the snapshot was validated before it was copied.

2) The similar things happened on the search node: the same index
which was opened OK during last night nodes recycle could not be
opened due to the same exception. The search node does not update

In my case, the index was "validated" before, and it became
invalidate in a later time. It seems it happened only when we
restart the application. When the exception happen, the file did
not exist in the index.


This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

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

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 20 | next ›
Discussion Overview
groupdev @
postedJul 7, '08 at 7:17a
activeJul 14, '08 at 8:18p



site design / logo © 2021 Grokbase