[email protected]
[Top] [All Lists]

Re: Lucene 2.2, NFS, Lock obtain timed out

Subject: Re: Lucene 2.2, NFS, Lock obtain timed out
From: "Patrick Kimber"
Date: Fri, 29 Jun 2007 15:45:00 +0100
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.


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:

To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

<Prev in Thread] Current Thread [Next in Thread>