[ 
https://issues.apache.org/jira/browse/LUCENE-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973363#comment-13973363
 ] 

Uwe Schindler commented on LUCENE-5612:
---------------------------------------

Thanks.
To run this after our standard test suite, wee will need to add a new target 
named "test" that is empty and depends on "common.test" and 
"test-lock-factory". we would just need a way to run this for all
I am not yet happy about the sleep 1, because slower computers may take longer. 
Is there a way to synchronize this without waiting? Maybe once the lock server 
is online and has bound to port, it prints the port number (a random one) to 
the file. The lockveryify clients just wait for the file to appear and read the 
port number and then start to hammer against the lock dir.

> LockStressTest fails always with NativeFSLockFactory
> ----------------------------------------------------
>
>                 Key: LUCENE-5612
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5612
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.8
>
>         Attachments: LUCENE-5612-instant-crush.patch, 
> LUCENE-5612-instant-crush.patch, LUCENE-5612-tester.patch, 
> LUCENE-5612-tester.patch
>
>
> I was looking at this, because i wanted to remove the static map inside 
> NativeFSLockFactory (no particular reason: it just smells bad, we require 
> java7, and you get overlappingexception as of java6 so its unnecessary).
> Before changing any code, i wanted to run lockstresstest first, just to 
> ensure it works: but it fails always. Simple works fine always.
> Exception in thread "main" java.lang.RuntimeException: 
> java.lang.RuntimeException: lock was double acquired at 
> org.apache.lucene.store.VerifyingLockFactory$CheckedLock.verify(VerifyingLockFactory.java:67)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to