My answer is inline.
Michael McCandless-2 wrote:
>
> Yajun Liu (JIRA) <[EMAIL PROTECTED]> wrote:
>
> Can you double check which underlying version of Lucene you are
> using? Those source file/line numbers don't line up to a stock 2.1
> release as far as I can tell.
>
> YL>> The lucene library comes with Solr. The jar file is
> lucene-core-2007-05-20_00-04-53.jar. I compared the source code of
> IndexReader which is close to Lucene 2.2, not 2.1
>
> This part is odd:
>
>> 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.
>
> If I understand the steps correctly, once and index is created,
> verified (by opening an IndexReader) and copied up to a snapshot, that
> snapshot is never changed by Lucene (opened by an IndexWriter, or
> IndexReader that does delete/setNorm)? Yet somehow all 3 become
> corrupt at the same time (that exception is hit when opening an
> IndexReader)?
>
> YL>> That's correct. Here is the sudo code of taking a snapshot:
> create a tmp directory /var/tmp/snapshot_timestamp
> int rety = 0;
> while (retry++ < 10) {
> copy index to /var/tmp/snapshot_timestamp
> try {
> IndexReader reader =
> IndexReader.open(/var/tmp/snapshot_timestamp/index);
> reader.close();
> } catch (IOException e) {
> delete /var/tmp/snapshot_timestamp/index
> continue;
> }
> }
>
> Did you say IndexReader also does delete? If that is the case, then the
> snapshot that is "validated" by IndexReader could be "invalidated" by this
> deletion. That could explain all the snapshots become corrupted.
>
>
> Also:
>
>> 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
>> index.
>
> Again nothing makes changes to these copies either, yet they suddenly
> starting hitting that same exception?
>
> YL>> correct. Nothing change on the search node.
>
> Are you really sure, when you go to open the snapshots, that you're
> actually specifying the right directory each time? It seems
> particularly odd for all 3 snapshots to hit the same exception at the
> same time.
>
> YL>> very sure.
>
> Another question: is it possible you are reopening your readers on an
> index dir while rsync is still copying to that index dir? That could
> easily
> lead to exceptions like this....
>
> YL>> index was rsync to a /var/tmp/rsync_tmp directory. When rsync is
> done, it is moved to a directory and then search node open indexreader on
> it.
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-jira--Created%3A-%28LUCENE-1328%29-FileNotFoundException-in-tp18311277p18323050.html
Sent from the Lucene - Java Developer mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
