Skip to main content
NetApp Knowledge Base

Performance issues caused by long CP

  1. Last updated
  2. Save as PDF
Views:
39
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9

Issue

  • Long CP was observed on node 2 the service was delayed.
  • EMS logs raid.perf.stats.opTimedOut right before the long CP

[?] Fri May 23 09:45:00 +0900 [node02: config_thread: raid.perf.stats.opTimedOut: debug]: Operation config_get_attributes_obj took 65808 ms to complete on the D-blade.

[?] Fri May 23 09:45:00 +0900 [node02: config_thread: raid.perf.stats.opTimedOut: debug]: Operation config_get_attributes_obj took 16641187 ms to complete on the D-blade.

[?] Fri May 23 09:45:00 +0900 [node02: wafl_exempt06: wafl.cp.toolong: error]: Aggregate ISCSI10_node2_aggr1 experienced a long CP.

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.