lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5612) LockStressTest fails always with NativeFSLockFactory
Date Fri, 18 Apr 2014 13:35:15 GMT


Uwe Schindler commented on LUCENE-5612:

bq. Now how will Mike be able to test NFS 

LOL. I'll readd the possibility to use another bind host and connect host. But default to I will now work on making the socket communication better without creating new
connections over an over.

Robert, did you try the latest patch? Does it work well for you?

If we fix the underlying bug that makes the crusher crush, can we do this in a separate patch?
I think the LockTester and the fix here are 2 separate things.

> LockStressTest fails always with NativeFSLockFactory
> ----------------------------------------------------
>                 Key: LUCENE-5612
>                 URL:
>             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-more-sophisticated-crusher.patch, LUCENE-5612-more-sophisticated-crusher.patch,
LUCENE-5612-more-sophisticated-crusher.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$CheckedLock.verify(

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message