[
https://issues.apache.org/jira/browse/KARAF-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308340#comment-17308340
]
ASF GitHub Bot commented on KARAF-7074:
---------------------------------------
jbonofre opened a new pull request #1336:
URL: https://github.com/apache/karaf/pull/1336
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Resolver parallelism can fail on kubernetes as the resolverParallelism is not
> accurate
> --------------------------------------------------------------------------------------
>
> Key: KARAF-7074
> URL: https://issues.apache.org/jira/browse/KARAF-7074
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> When building Karaf on kubernetes (on a pod), the {{resolverParallelism}} can
> be "bad" depending of the number of vCPU and the features dependencies.
> The {{resolverParallelism}} is computed like this:
> {code:java}
> int resolverParallelism = Math.max(1,
> Runtime.getRuntime().availableProcessors()); {code}
> Actually, if the features are not really sequential (features dependencies),
> the resolution will fail with 1 (if we have a single vCPU). The default
> should be at least 2.
> It's better to use {{-1}} by default and then using resolver with default
> parallelism, and let the user defines the {{resolverParallelism}} by
> parameter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
