You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by javabuddy <ma...@roomity.com> on 2005/10/11 18:44:34 UTC

Lucene and Quartz

Hi,

I have the indexing process running in an quartz environment. (on a clustered two boxes)

I made sure that the Indexing doesnt runs simultaneously on both the boxes.

But suddenly I am start getting "FileNotFoundException" on the indexing process. From that pont on the indexes are of no use. I need to start the indexing from scratch.

I need to know a couple of things....

1. Is there a way to regain the indexes after getting "FileNotFoundException" .

2. What is wrong in having the indexing process run across two machines..

Will the IndexWriter.optimize() method refresh the indexes, on top of optimizing it????

- Gana.


------------------------------------------------------------------
<a href="http://Lucene_Java_User_List.roomity.com">roomity.com</a>
Your Roomity Broadband Webapp ~~1129049073830~~
------------------------------------------------------------------

Re:Lucene and Quartz

Posted by javabuddy <ma...@roomity.com>.
Thanks for the reply.

Here is what happens...

I have 2 boxes A and B. And the indices are created on Machine C.

The directory of the index is mounted on both the machines A and B.

We have quartz using JDBCJobStore. So index creation runs on either one of the box. SO when index creation job is over on machine A, and when machine B starts it throws FileNotFoundException on one of the index file like _fkm.idx, (this is an sample file name)

So y is this happening. I made sure that the jobs for creating index are not running at the same time. 

My doubt is when machine A completes, the indexes that are updated or generated are not reflected on to the machine B. Bcos of the mount.

Can you help me out???

- javabuddy.


------------------------------------------------------------------
<a href="http://Lucene_Java_User_List.roomity.com">roomity.com</a>
Your Roomity Broadband Webapp ~~1129079515196~~
------------------------------------------------------------------