メインコンテンツまでスキップ

Azure CVO の速度低下とリブートが blaadeAggrTable_iterartor でタイムアウトして失敗しました: next()

Views:
2
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
perf
Last Updated:

環境

  • Cloud Volumes ONTAP(CVO)
  • Microsoft Azure
  • シングル ノード
  • Fabric Pool から Azure のページ Blob への移動
  • SnapCenter 
  • SnapVault
  • Microsoft Structured Query Language ( 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

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.
Scan to view the article on your device