[ https://issues.apache.org/jira/browse/LUCENE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862735#action_12862735 ]
Michael McCandless commented on LUCENE-2421: -------------------------------------------- I guess since it's a last resort "we think will very rarely happen in practice" thing... we can leave it @ 100 msec. Just makes me nervous :) Libraries shouldn't be doing things like sleeping on you (for so long)... Hmm -- after that sleep, we still throw LockReleaseFailedException if we are still unable to delete it? Isn't it "harmless" if we can't delete it? Also, rather than swallowing the InterruptedException, you should immediately throw ThreadInterruptedException -- we fixed Lucene a while back to not swallow this exception (LUCENE-2053). > Hardening of NativeFSLock > ------------------------- > > Key: LUCENE-2421 > URL: https://issues.apache.org/jira/browse/LUCENE-2421 > Project: Lucene - Java > Issue Type: Improvement > Components: Index > Reporter: Shai Erera > Assignee: Shai Erera > Fix For: 3.1 > > Attachments: LUCENE-2421.patch > > > NativeFSLock create a test lock file which its name might collide w/ another > JVM that is running. Very unlikely, but still it happened a couple of times > already, since the tests were parallelized. This may result in a false > exception thrown from release(), when the lock file's delete() is called and > returns false, because the file does not exist (deleted by another JVM > already). In addition, release() should give a second attempt to delete() if > it fails, since the file may be held temporarily by another process (like > AntiVirus) before it fails. The proposed changes are: > 1) Use ManagementFactory.getRuntimeMXBean().getName() as part of the test > lock name (should include the process Id) > 2) In release(), if delete() fails, check if the file indeed exists. If it > is, let's attempt a re-delete() few ms later. > 3) If (3) still fails, throw an exception. Alternatively, we can attempt a > deleteOnExit. > I'll post a patch later today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org