Skip to main content
NetApp Knowledge Base

High Worker Node CPU Usage Caused by Trident Orphaned Volumes Referencing Deleted Backend

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

Applies to

  • NetApp Astra Trident CSI Driver
  • Kubernetes / OpenShift environments
  • ONTAP SAN/NAS backends

Issue

Worker nodes running Trident CSI controller pods exhibit sustained high CPU utilization (up to 100%). 

leading to:

  • Cluster-wide performance degradation
  • Application disruption across multiple pods
  • Increased latency in provisioning and deletion workflows
Observed Log Patterns:

From Trident controller logs:

level=error msg="Invalid backend state." expectedState=online/deleting state=failed workflow="core=node_reconcile"
msg="Unable to delete snapshot from backend."
error="backend <backend-name> is not Online or Deleting"
msg="Unable to delete volume from backend."
error="backend <backend-name> is not Online or Deleting"
  • These errors repeat continuously (high frequency retries)
  • Controller enters a persistent reconcile loop

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.