Thanks Mike.
Shai
On Sat, Aug 15, 2009 at 12:49 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> You could also use NoLockFactory.
>
> Disabling locks just means Lucene stops checking if another writer has
> the index open (the write.lock file).
>
> It's extremely dangerous to do, un
You could also use NoLockFactory.
Disabling locks just means Lucene stops checking if another writer has
the index open (the write.lock file).
It's extremely dangerous to do, unless you are absolutely certain your
application level locking properly implements the protection. It will
quickly lead
Hi
If I can guarantee only one JVM will update an index (not at a time - truly
just one JVM), can I disable locks, or is it really necessary only for
read-only devices? If I disable locks, will I see any performance
improvements?
Thanks
Shai
