Michael McCandless wrote:
/This means the segments files is referencing a segment named _1j8s and
in trying to load that segment, the first thing Lucene does is load the
"field infos" (_1j8s.fnm). It tries to do so from a compound file (if
you have it turned on & it exists), else from the filesystem directly.
/Michael,
For a moment I wondered what exactly do you mean by "compound file"?
Then I read http://lucene.apache.org/java/docs/fileformats.html and got
the idea.
I do not have access to that specific machine that all this is happening at.
It is a 80x86 machine running Win 2003 server;
Sorry, but they neglected my question about the index is stored on a
Local FS or on a NFS.
I was only able to obtain a directory listing of the index dir and guess
what - there's no a /*_1j8s.cfs * /file at all!
Pitty, I can't have a look at segments file, but I guess it lists the _1j8s
Given these scarce resources, can you give me some further advise about
what has happened and what can be done to prevent it from happening again?
Regards,
Stanislav
Stanislav Jordanov wrote:
What might be the possible reason for an IndexReader failing to open
properly,
because it can not find a .fnm file that is expected to be there:
This means the segments files is referencing a segment named _1j8s and
in trying to load that segment, the first thing Lucene does is load
the "field infos" (_1j8s.fnm). It tries to do so from a compound file
(if you have it turned on & it exists), else from the filesystem
directly.
Which version of Lucene are you using? And which OS are you running on?
Is this error easily repeated (not a transient error)? Ie,
instantiating an IndexSearcher against your index always causes this
exception? Because, this sort of exception is certainly possible when
Lucene's locking is not working correctly (for exmple over NFS), but
in that case it's typically very intermittant.
Could you send a list of the files in your index?
The only thing that comes to my mind is that last time the indexing
process was not shut down properly.
Is there a way to revive the index or everything should be reindexed
from scratch?
Hmmm. It's surprising that an improper shutdown caused this because
when the IndexWriter commits its change, it first writes all files for
the new segment and only when that's successful does it write a new
segments file referencing the newly written segment. Could you
provide some more detail about your setup and how the improper
shutdown happened?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
