I cannot remember the answer I got, but I asked the same question after the code was changed to put locks in java.io.tmpdir. Because I have an application that deals with a lot of indices simultaneously, I felt like this will make things more difficult in cases where you have stale locks, etc. Try the archive, though, as I seem to recall that somebody, Doug or Scott gave me the answer.
Otis --- petite_abeille <[EMAIL PROTECTED]> wrote: > Hello, > > 10/01 11:25:41 (Warning) IndexWriter.<init>: java.io.IOException: > Index > locked for write: > [EMAIL PROTECTED]:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\lucene- > 08d0626209019ccc9327ba6fb063c456-write.lock > > Is there a straightforward way to figure out which lock belong to > which > index? The lock name seems to be a MD5 digest of the index's > directory > canonical path (or at least this is what getLockPrefix() looks like). > > Previously, the locks where located alongside the indices... so it > was > pretty trivial to know which lock belong to which index... but now > that > they are all dumped into java.io.tmpdir this is getting cumbersome... > > why the move to tmpdir in the first place? This seems to be a very > gratuitous change, which only complicate things without providing any > > obvious value... > > Or perhaps I'm missing something? > > Cheers, > > PA. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
