Skip to main content
NetApp Knowledge Base

Trident slow Volume Attachment after Data Center Failover

  1. Last updated
  2. Save as PDF
Views:
9
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • AFF
  • AFF-A90
  • 9.16.1P12 CLUSTER-MODE MCC-IP
  • OpenShift Virtualization (OSV)  
  • Trident 25.10

Issue

After a data center failover in an OpenShift Virtualization environment using Trident with iSCSI (ontap-san-economy backend), the attachment process for restarting 600 virtual machines in the affected cluster is taking an extremely long time. The Trident Controller startup and initialization takes about 1.5 hours, and after an additional 1.5 hours, only about 50 of the 600 VMs are running. The environment consists of 84 Trident backend configurations and 1377 VMs.  

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.