Proxy container in elasticsearch pods restarting due to oom-kill in OpenShift Container Platform 4

Solution Verified - Updated -


  • On all OpenShift 4.5 environments we are observing, that the container proxy in all pods elasticsearch-cd[m] frequently (some more than once a day) are OOMKilled and therefore restarted.
  • Elasticsearch proxy container OOMKilled
  • We have a 250 node cluster with very large infra nodes for elasticsearch. Elasticsearch pods are continuously getting oom-killed due to cgroup limits causing issues with large scale logging testing and missing messages.


  • Red Hat OpenShift Container Platform (RHOCP) 4.5

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