[
https://issues.apache.org/jira/browse/LUCENE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831984#comment-13831984
]
Mark Miller commented on LUCENE-5349:
-------------------------------------
Robert pointed me to http://jira.pentaho.com/browse/BISERVER-4809
Which mentions:
{quote}Ivy caching is made up of two caches, a repository cache (holds the
artifacts), and a resolution cache (holds metadata about the resolved
artifacts).
The repository cache can be accessed by multiple processes safely using the
artifact-lock lock strategy.
The resolution cache can NEVER be accessed by multiple processes safely,
regardless of what lock strategy is in use. {quote}
> Ivy's resolution cache can easily corrupt and cause premature end of file
> errors.
> ---------------------------------------------------------------------------------
>
> Key: LUCENE-5349
> URL: https://issues.apache.org/jira/browse/LUCENE-5349
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 5.0, 4.7
>
> Attachments: LUCENE-5349.patch
>
>
> If probably know this problem well if you run with a few executors on your
> jenkins setup.
> Really annoying.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
