Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-7074

Resolver parallelism can fail on kubernetes as the resolverParallelism is not accurate

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.3.1
    • karaf
    • None

    Description

      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:

      int resolverParallelism = Math.max(1, Runtime.getRuntime().availableProcessors()); 

      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.

      Attachments

        Activity

          People

            jbonofre Jean-Baptiste Onofré
            jbonofre Jean-Baptiste Onofré
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: