跳转到主内容

如何识别卷名称已截断的高延迟卷?

Views:
6
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf<a>2009年353452</a>
Last Updated:

适用场景

  • ONTAP 9
  • 服务质量 (QoS)
  • 超过15个字符的卷名称
  • 自动卷流工作负载
  • 工作负载ID (WID)

问题描述

可以使用以下命令行界面命令快速识别延迟较高的卷。

  • qos statistics volume latency show
  • qos statistics volume performance show
  • qos statistics workload latency show
  • qos statistics workload performance show

     

这将在命令输出的第一列(Workload 列)中显示延迟最高的前10个工作负载。

示例:

Cluster::> qos statistics volume latency show
Workload     ID   Latency    Network   Cluster   Data     Disk     QoS       NVRAM    Cloud 
---------------  ------ ----------  ---------- ---------- ---------- ---------- ----------  ---------- ---------- 
-total-      -     1277.00us   251.00us   0ms     553.00us   473.00us   0ms     0ms     0ms 
VOL_VMware_te.. 19547 41.50ms   2.69ms    9.00us   29.68ms   9.13ms    0ms     0ms     0ms    
VOL_VMware_te.. 5658 16.00ms   3.58ms    8.00us   11.80ms   619.00us   0ms     0ms     0ms      
vol1-wid28961   28961  13.28ms    3.67ms    3.00us    9.44ms   159.00us   0ms     0ms     0ms 

注:

  • WID19457 是指卷的自动卷工作负载 VOL_VMWARE_testing1
  • WID 5658 是指卷的自动卷工作负载 VOL_VMWARE_testing2
  • 它们在截断后的显示方式相同 

这是预期行为- Workload 列中最多可显示15个字符。任何超过15个字符的工作负载将被截断为13个字符、并在末尾加上两个点

 

如果在类似的命名约定 Workload中存在多个长卷名称、则可能很难缩小所需的确切卷范围、因为多个卷可能会共享截断后列中显示的相同工作负载名称。

本文提供了一种根据 ID 列中显示的WID查找相关卷的方法。 

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.