Marvin Humphrey wrote:
On Jan 17, 2007, at 3:42 AM, Grant Ingersoll wrote:
Also, I'm curious as to how many people use NFS in live systems.
KS has the same problems Lucene does, and it's a common enough complaint
that I've added an FAQ item. It's an important issue.
I agree it's important. Our users naturally assume KS and Lucene are
usable over NFS (or any filesystem). And NFS is obviously very common
since it's the standard remote filesystem for Unix.
The less we rely on filesystem specifics such as "what happens if you
delete an open file", the more portable we will be.
However, I don't have the faintest idea how to solve it.
So unless someone comes up with something simple and brilliant, I don't
think it should stand in the way, either.
This is the solution I have in mind for LUCENE-710: change the
IndexFileDeleter so that instead of always immediately deleting the
last commit when a new commit happens, allow some time before doing
so. This way readers have a chance to refresh. The actual time would
be settable by the developer. So if you set it to 6 hours, then, a
commit would remain usable for at least 6 hours after it had been
obsoleted by a new commit. This means if you can ensure your readers
refresh within 6 hours of a new commit happening, then the writer will
never delete an "in-use" commit.
I don't think we should necessarily hold up 2.1 for this change,
though.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
