Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-1524

[JAVA8] Recognize JAVA_CORE_LIMIT env var setting or replace it with CONTAINER_CORE_LIMIT in the documentation

XMLWordPrintable

    • CLOUD Maintenance Sprint 12

      Current JAVA_CORE_LIMIT variable description:

      Core limit as described in
https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt.
Used to configure the number of GC threads and parallelism for
ForkJoinPool.  Defaults to container core limit.

      The above description suggests the following:

      • JAVA_CORE_LIMIT variable can be set to configure number of GC threads and parallelism for ForJoinPool (when CONTAINER_CORE_LIMIT is unset),
      • JAVA_CORE_LIMIT will use setting from CONTAINER_CORE_LIMIT, when CONTAINER_CORE_LIMIT is set

      But this doesn't correspond to current behaviour:

      • When CONTAINER_CORE_LIMIT is set (and JAVA_CORE_LIMIT is unset) CONTAINER_CORE_LIMITs are used for number of GC threads and parallelism configuration (OK),
      • When CONTAINER_CORE_LIMIT is unset (and JAVA_CORE_LIMIT is set) the variable has no effect (number of GC threads and parallelism for ForkJoinPool isn't configured at all).

              rhn-support-fspolti Filippe Spolti
              rhn-jlieskov Ján Lieskovský (Inactive)
              Tomas Remes Tomas Remes
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: