Pod performance degradation after node reboot due to low memory limit
Issue
- After an OpenShift worker node is rebooted, applications in existing Pods run significantly slower.
- The slowdown is observed on the very first run and on every subsequent run inside the same Pod.
- If the Pod is deleted and recreated (for example, by
oc delete pod... or by a Deployment rolling-update), performance immediately returns to normal.
Environment
- Red Hat OpenShift Container Platform
- 4
- Pods with application workloads that read large files
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.