Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-1720

evictionLimits.total=2 should be set in kubeDescheduler by default when DevKubeVirtRelieveAndMigrate profile is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       

      If a VM migration takes a long, the descheduler may attempt to evict more VMs in parallel. We've seen up to 5 evictionRequests at one point of time:

      I0617 06:58:50.396955       1 descheduler.go:403] "Number of evictions/requests" totalEvicted=0 evictionRequests=5 

       

      Since KubeVirt allows only 2 concurrent migrations per node by default, additional migration jobs remain stuck in a Pending state, waiting for available migration slots

      When using the DevKubeVirtRelieveAndMigrate profile, we should limit evictions by default (set 'evictionLimits.total=2') to match the KubeVirt migration limit and avoid unnecessary evictions.

       

              stirabos Simone Tiraboschi
              dshchedr@redhat.com Denys Shchedrivyi
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: