Too many haproxy processes running in default-router pod on RHOCP node

Solution Verified - Updated -

Issue

  • High number of haproxy processes in default-router pod causing high load average on RHOCP node.
  • Ingress node memory consumption is growing until all memory is consumed, causing OOM (out-of-memory) killing of random processes and overall ingress node outage.
  • Router pods are intermittently restarting without explanation a few times every day/hours.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content