Hi Mark I just ran my test again... and the error occurred after 10 minutes - which is the time when my deletion policy is triggered. So... I think you might have found the answer to my problem.
I will spend more time looking at it on Monday. Thank you very much for your help and enjoy your weekend. Patrick On 29/06/07, Mark Miller <[EMAIL PROTECTED]> wrote:
If your getting java.io.FileNotFoundException: /mnt/nfstest/repository/lucene/lucene-icm-test-1-0/segments_h75 within 2 minutes, this is very odd indeed. That would seem to imply your deletion policy is not working. You might try just using one of the nodes as the writer. In Michaels comments, he always seems to mention the pattern of one writer many readers on nfs. In this case you could use no LockFactory and perhaps gain a little speed there. - Mark Patrick Kimber wrote: > Hi Mark > > Yes, thank you. I can see your point and I think we might have to pay > some attention to this issue. > > But, we sometimes see this error on an NFS share within 2 minutes of > starting the test so I don't think this is the only problem. > > Once again, thanks for the idea. I will certainly be looking to > modify the code in the LuceneIndexAccessor to take this into account. > > Patrick > > On 29/06/07, Mark Miller <[EMAIL PROTECTED]> wrote: >> This is an interesting choice. Perhaps you have modified >> LuceneIndexAccessor, but it seems to me (without knowing much about your >> setup) that you would have odd reader behavior. On a 3 node system, >> if you >> add docs with node 1 and 2 but not 3 and your doing searches against >> all 3 >> nodes, node 3 will have old readers opened until you add a doc to >> node 3. >> This is an odd consistency issue (node 1 and 2 have current views >> because >> you are adding docs to them, but node 3 will be stale until it gets a >> doc), >> but also if you keep adding docs to node 1 and 2, or just plain add >> no docs >> to node 3, won't node 3's reader's index files be pulled out from >> under it >> after 10 minutes? Node 3 (or 1 and 2 for that matter) will not give >> up its >> cached readers *until* you add a doc with that particular node. >> >> Perhaps I am all wet on this (I havn't used NFS with Lucene), but I >> think >> you may need to somehow coordinate the delete policy with the >> LuceneIndexAccessor on each node. >> >> This may be unrelated to your problem,and perhaps you get around the >> issue >> somehow, but just to throw it out there... >> >> - Mark >> >> On 6/29/07, Patrick Kimber < [EMAIL PROTECTED]> wrote: >> > >> > >> > >> > I am using the Lucene Index Accessor contribution to co-ordinate the >> > readers and writers: >> > >> > >> http://www.nabble.com/Fwd%3A-Contribution%3A-LuceneIndexAccessor-t17416.html#a47049 >> >> > >> > >> > > --------------------------------------------------------------------- > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
