Skip to main content
NetApp Knowledge Base

Azure CVO slowness and reboot failed with timeout on bladeAggrTable_iterartor::next()

  1. Last updated
  2. Save as PDF
Views:
108
Visibility:
Public
Votes:
1
Category:
cloud-volumes-ontap-cvo
Specialty:
perf
Last Updated:

Applies to

  • Cloud Volumes ONTAP(CVO)
  • Microsoft Azure
  • Single Node
  • Fabric Pool to Azure page blob
  • SnapCenter 
  • Snapvault
  • Microsoft Structured Query Language (SQL)

Issue

  • Azure single node CVO slowness and subsequent reboot to mitigate slowness temporarily failed with error as timeout on bladeAggrTable_iterartor::next()
 
EMS.log:
 
Sun Jan 01 2022 00:00:00 +00:00 system node reboot :: Error: Timeout: Operation "bladeAggrTable_iterator::next()" took longer than 25 seconds to complete [from mgwd on node "CVOCluster-01" (VSID: -1) to vldb at 127.0.0.1]
 
  • Also seen are panics below:
 
EMS.log:
 
Sun Jan 01 2022 00:00:00 [CVOCluster-01: ThreadHandlerun: sk.panic:alert]: Panic String: kma: object 0xfffff80700000000 is not allocated in SK process ThreadHandlerun on release 9.9.0 (C)

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.