Skip to main content
NetApp Knowledge Base

FlexGroup has high latency due to all workload on single constituent

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

Applies to

  • ONTAP 9
  • FlexGroups

Issue

  • Increased latency observed for "other" ops (specifically READDIR but can be seen on GETATTR and other metadata ops) on the FlexGroup parent
  • Write throughput may seem to be less than total
    • Example: Normally a 6 node A800 cluster may see 10 GB/s writes before hitting Data Processing latency, but throughput may only be 1-2 GB/s for writes
  • Latency may be seen on a single constituent
  • Reads or Writes can show a large increase in latency when there is a large increase in Read/Write workload within a single constituent.
  • Latency is seen as Data Processing or Data in qos statistics volume latency show
  • Latency may shift between constituent volumes in rapid succession if multiple directories are read or written to

 

 

 

 

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.