跳转到主内容

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

INSIGHT Japan :2023年 1月25日(水)ANAインターコンチネンタルホテル開催 へ参加・申込を行う

Azure CVO 速度较慢并重新启动失败, bladeAggrTable_迭 代器上发生超时:: next( )

Views:
4
Visibility:
Public
Votes:
1
Category:
cloud-volumes-ontap-cvo
Specialty:
perf
Last Updated:

适用场景

  • Cloud Volumes ONTAP ( CVO )
  • Microsoft Azure
  • 单节点
  • Fabric Pool 到 Azure 页面 Blob
  • SnapCenter 
  • Snapvault
  • Microsoft 结构化查询语言( SQL )

问题描述

  • Azure 单节点 CVO 速度较慢,并在此后重新启动以缓解速度较慢的问题,但暂时失败,并显示错误为超时 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]
 
  • 下面还会显示一些崩溃:
 
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

Scan to view the article on your device