Skip to main content
NetApp Knowledge Base

Trident Pod Consumes 100% Physical CPU on OpenShift Node

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:

Applies to

  • NetApp Trident CSI Driver
  • OpenShift 4.x (specifically 4.19)
  • ONTAP SAN/NAS backends (ONTAP 9.14.1P1 and lower)
  • AFF-C250 and similar ONTAP systems

Issue

A Trident node pod (trident-node-linux-<pod>) in an OpenShift cluster consumes 100% of the physical CPU on its node, causing:

  • Cluster-wide performance degradation
  • Application disruption (VMs on the node became unresponsive)
  • Increased latency in provisioning/deletion workflows

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.