Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2184

NetObserv controller pod gets OOM killed on very large cluster

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 270, NetObserv - Sprint 271, NetObserv - Sprint 272, NetObserv - Sprint 273, NetObserv - Sprint 274, NetObserv - Sprint 275, NetObserv - Sprint 276
    • Proposed
    • Bug Fix
    • Hide
      Before this update, insufficient memory allocation caused network observability controller pod out-of-memory (OOM) kills in high-performance scenarios. As a consequence, the network observability controller pod consumed excessive memory, causing OOM kills for 500 nodes, impacting user performance. With this release, the network observability CSV memory limit has been increased to prevent OOM kills. As a result, the network observability controller pod no longer OOM kills for 500 nodes, improving stability.
      Show
      Before this update, insufficient memory allocation caused network observability controller pod out-of-memory (OOM) kills in high-performance scenarios. As a consequence, the network observability controller pod consumed excessive memory, causing OOM kills for 500 nodes, impacting user performance. With this release, the network observability CSV memory limit has been increased to prevent OOM kills. As a result, the network observability controller pod no longer OOM kills for 500 nodes, improving stability.

      Description of problem:

      NetObserv controller pod gets OOM killed for 500 nodes perf scenario

      Steps to Reproduce:

      1. Deploy Network Observability operator
      2. Run 500 nodes perf scenario
      

      Actual results:

      Operator pod gets OOM killed

      Expected results:

      Operator pod should not get OOM killed

       

      Upon doubling the memory in NetObserv CSV, the pod runs fine

      Resources:
                        Limits:
                          Memory:  800Mi
                        Requests:
                          Cpu:     100m
                          Memory:  200Mi 

              jtakvori Joel Takvorian
              rhn-support-aramesha Amogh Rameshappa Devapura
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: