[
https://issues.apache.org/jira/browse/LUCENE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705500#comment-14705500
]
Mark Miller commented on LUCENE-6743:
-------------------------------------
Supposedly part of this issue (leaving locks behind with artifact-lock impl)
was fixed in 2.3, but you can still see it happen in 2.3 and 2.4.:
https://issues.apache.org/jira/browse/IVY-1388?filter=-3
> Allow Ivy lockStrategy to be overridden by system property.
> -----------------------------------------------------------
>
> Key: LUCENE-6743
> URL: https://issues.apache.org/jira/browse/LUCENE-6743
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: Trunk, 5.4
>
> Attachments: LUCENE-6743.patch
>
>
> The current hard code lock strategy is imperfect and can fail under parallel
> load. With Ivy 2.4 there is a better option in artifact-lock-nio. We should
> allow the lock strategy to be overrideen like the resolutionCacheDir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
