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

[JDG7] CPU cores are not reflecting set quotas while running in a pod

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • JDG71 1.3.0.GA
    • JDG7

    Description

      JDG shows this message while starting:

      INFO [org.wildfly.extension.io] (ServerService Thread Pool – 20) WFLYIO001: Worker 'default' has auto-configured to 112 core threads with 896 task threads based on your 56 available processors.

      This is with CPU limits in place for 500 millicores.

      From 'Open Java Console' from pod, information from MBean java.lang:type=OperatingSystem shows 56 cpus.

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-2631 [JDG72] Upgrade images to 7.2.1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-9421 Server workers configuration not applied

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-9091 Replace Runtime.getRuntime().availableProcessors() usage with a cgroups quota-aware implementation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          JDK-8146115 Loading...

          Activity

            People

              ttarrant@redhat.com Tristan Tarrant
              rhn-support-trogers Travis Rogers (Inactive)
              Pavel Drobek Pavel Drobek
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: