As per 1.3 (or was it 1.4) Lucene migrated to using java.iot.tmpdir to store the locks for the index.

While under most situations this is save a lot of application servers change java.io.tmpdir at runtime.

Tomcat is a good example. Within Tomcat this property is set to TOMCAT_HOME/temp..

Under this situation if I were to create two IndexWriters within two VMs and try to write to the same index the index would get corrupted if one Lucene instance was within Tomcat and the other was within a standard VM.

I think we should consider either:

1. Using out own tmpdir property based on the given OS.
2. Go back to the old mechanism of storing the locks within the index basedir (if it's not readonly).


Thoughts?

--

Please reply using PGP.

http://peerfear.org/pubkey.asc NewsMonster - http://www.newsmonster.org/
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to