Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38819

Calculation of Overcommit is wrong

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.16.z
    • Documentation / Node
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Informational
    • None
    • None
    • None
    • None
    • OSDOCS Sprint 267, OSDOCS Sprint 268
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Calculation of Overcommit is wrong

      Version-Release number of selected component (if applicable):

      4.16 

      How reproducible:

      Every time

      Steps to Reproduce:

      https://docs.openshift.com/container-platform/4.16/nodes/clusters/nodes-cluster-overcommit.html
      
      states:
      
      Scheduling is based on resources requested, while quota and hard limits refer to resource limits, which can be set higher than requested resources. The difference between request and limit determines the level of overcommit; for instance, if a container is given a memory request of 1Gi and a memory limit of 2Gi, it is scheduled based on the 1Gi request being available on the node, but could use up to 2Gi; so it is 200% overcommitted.
      
      ====
      
      Going from 1GBi to 2Gbi is 100% overcommit not 200%. 0% overcommit means you're within the requested resources. Going over with 5% would mean going to 1.05Gi etc. which means going over by 1Gi is 100%

      Actual results:

          

      Expected results:

          

      Additional info:

          

              ocp-docs-bot OCP DocsBot
              rh-sa-plarsen Peter Larsen
              None
              None
              Min Li Min Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: